Agent Skills › LLMQuant/quant-mind › quantmind-dev

quantmind-dev

GitHub

QuantMind代码库贡献工作流指南，涵盖提交规范、PR格式及模块开发。提供commit、PR、组件开发等参考路径，强调验证脚本执行与测试要求。

.agents/skills/quantmind-dev/SKILL.md LLMQuant/quant-mind

Trigger Scenarios

准备提交代码创建或更新Pull Request 开发或重构quantmind模块编写或编辑contexts文档

Install

npx skills add LLMQuant/quant-mind --skill quantmind-dev -g -y

More Options

Non-standard path

npx skills add https://github.com/LLMQuant/quant-mind/tree/master/.agents/skills/quantmind-dev -g -y

Use without installing

npx skills use LLMQuant/quant-mind@quantmind-dev

指定 Agent (Claude Code)

npx skills add LLMQuant/quant-mind --skill quantmind-dev -a claude-code -g -y

安装 repo 全部 skill

npx skills add LLMQuant/quant-mind --all -g -y

预览 repo 内 skill

npx skills add LLMQuant/quant-mind --list

SKILL.md

Frontmatter

{
    "name": "quantmind-dev",
    "description": "Contributor workflow for the QuantMind codebase. Covers commit format, pull request format, and component development across quantmind\/ modules (knowledge, configs, preprocess, rag, flows, mind, utils) with tests, examples, and verification. Use when committing, opening a PR, or implementing\/refactoring QuantMind code."
}

QuantMind Dev

Development workflow for contributing to the QuantMind codebase.

Start Here

Use the repository contexts/README.md to select the development context for this contribution.
Read the repository root AGENTS.md or CLAUDE.md for the stable architecture constraints and the module map.
Read docs/README.md when the task adds, changes, or uses a public operation or public-network source.
When creating, updating, or triaging an issue or pull request, use the canonical repository label guidance.
Before writing or editing any GitHub body, follow the canonical GitHub writing style, including its no-hard-wrap rule.
Pick exactly one workflow reference below; do not load the others.

Select Workflow

Committing staged work → references/commit.md
Opening or updating a pull request → references/pull-request.md
Implementing or refactoring anything under quantmind/ → references/develop-components.md (read it before writing code)
Adding or editing a page under contexts/ → references/write-contexts.md

A feature task usually chains all three: develop → commit → pull request.

Rules

bash scripts/verify.sh is the deterministic required verification. Run it before every push and before marking a PR ready. The required .github/workflows/ci.yml workflow runs the same harness.
Public-network integrations have separate bounded smoke tests. .github/workflows/e2e.yml owns their scheduled, manual, and path-filtered component jobs. Run every applicable test listed in docs/README.md when changing that component and before publishing. External service availability must not block unrelated changes.
Keep docs/README.md as the single catalog of component smoke-test commands. A new live component adds a component-specific scripts/verify_<component>_e2e.py, a named job in the existing e2e.yml, precise PR path coverage, and one catalog row. When multiple live jobs exist, use GitHub-native per-job change detection so only affected jobs run. Do not add a separate workflow, generic E2E runner or registry, or base E2E class.
Never bypass pre-commit / pre-push hooks (--no-verify) unless the user explicitly authorizes it.
New features ship with a unit test and a focused example (see references/develop-components.md).
This skill is mirrored under .agents/skills/quantmind-dev/ and .claude/skills/quantmind-dev/; the copies are identical. When changing the skill, update both in the same change.

Boundaries

This skill is for contributing to QuantMind itself. It does not cover using QuantMind as a library in your own project.
Product decisions (new modules, new dependencies, API redesigns) need an issue and maintainer discussion first; do not encode them here.