鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

qa-commit

对代码提交进行全维度质量验证,覆盖技术规范、后端行为契约与前端验收标准,自动比对 Gherkin 场景和 AC 条款,执行静态检查、类型校验、测试运行及界面交互验证,结果为 GREEN 或 RED,并在失败时自动触发调试流程。

区块链
访问 GitHub
文档Skills.MD
name
qa-commit
description
Verify implementation against QA Contract (G#N, AC#N), auto-invoke debug on RED

QA Commit Skill

Verify that the current commit satisfies its assigned QA Contract criteria (G#N Gherkin scenarios and AC#N acceptance criteria). Returns GREEN (pass) or RED (fail, triggers debug).

When to Use

  • After pr-review passes, before git commit
  • During Agent Mode commit-level workflow
  • Manually with "use qa-commit skill"

Input: Commit Context

Before running, identify:

  1. Current commit from Commit Plan
  2. Assigned criteria: "Satisfies: G#X, AC#Y, ..."
  3. Related files being changed

Phase 1: Load QA Contract

Retrieve the assigned criteria for this commit:

▼
markdown
复制代码
## Commit: [Name] **Satisfies:** G#1, G#2, AC#1, AC#3 ### Criteria to Verify: - G#1: [Scenario description] - G#2: [Scenario description] - AC#1: [Acceptance criteria] - AC#3: [Acceptance criteria]

Phase 2: Technical Validation

Use Cursor tools for technical checks:

2.1 ReadLints

▼
text
复制代码
ReadLints: paths: [changed files]

Expect: No errors related to committed functionality

2.2 Type Safety

▼
bash
复制代码
npm run typecheck

Expect: Exit code 0

2.3 Related Tests (if exist)

▼
bash
复制代码
npm run test -- --grep "[feature name]"

Expect: All tests pass

Phase 3: Gherkin Verification (Backend - G#N)

For each G#N assigned to this commit:

3.1 Endpoint Existence

Verify the API endpoint exists and is implemented:

▼
text
复制代码
SemanticSearch: "Where is [endpoint] implemented?"

3.2 Response Shape

Check response matches expected schema:

▼
text
复制代码
Grep: "interface.*Response" in related files

3.3 Error Handling

Verify error cases are handled:

▼
text
复制代码
Grep: "throw|catch|error" in handler files

Gherkin Checklist

G#NScenarioStatusNotes
G#1[Name]PASS/FAIL[Details]
G#2[Name]PASS/FAIL[Details]

Phase 4: Acceptance Verification (Frontend - AC#N)

For each AC#N assigned to this commit:

4.1 Component Existence

Verify component is implemented:

▼
text
复制代码
Glob: **/*[ComponentName]*.tsx

4.2 Storybook Story (if AC involves visual)

Check Storybook story exists:

▼
text
复制代码
Glob: **/*[ComponentName]*.stories.tsx

4.3 Browser MCP Verification (if running)

For interactive acceptance criteria:

▼
text
复制代码
Browser MCP: 1. browser_navigate to Storybook URL 2. browser_snapshot to check state 3. browser_click/browser_type to test interaction 4. browser_take_screenshot for evidence

Acceptance Checklist

AC#NCriteriaStatusEvidence
AC#1[Criteria]PASS/FAIL[Screenshot/Notes]
AC#3[Criteria]PASS/FAIL[Screenshot/Notes]

Phase 5: Generate Verification Report

▼
markdown
复制代码
## Verification Report **Commit:** [Name] **Satisfies:** G#1, G#2, AC#1, AC#3 ### Technical Validation | Check | Status | |-------|--------| | ReadLints | PASS/FAIL | | TypeCheck | PASS/FAIL | | Tests | PASS/FAIL/SKIP | ### Gherkin Scenarios (Backend) | ID | Scenario | Status | Notes | |----|----------|--------|-------| | G#1 | [Name] | PASS/FAIL | [Details] | | G#2 | [Name] | PASS/FAIL | [Details] | ### Acceptance Criteria (Frontend) | ID | Criteria | Status | Evidence | |----|----------|--------|----------| | AC#1 | [Criteria] | PASS/FAIL | [Link/Notes] | | AC#3 | [Criteria] | PASS/FAIL | [Link/Notes] | ### Verdict **[GREEN / RED]** [If GREEN: All criteria verified, ready to commit] [If RED: Failed criteria listed, invoking debug skill]

Phase 6: Handle Verdict

GREEN Verdict

▼
markdown
复制代码
All criteria verified. Proceeding to git commit.

RED Verdict - Auto-Invoke Debug

▼
markdown
复制代码
**Verification failed. Auto-invoking debug skill.** ### Failed Criteria: - [G#N or AC#N]: [What failed] - [G#N or AC#N]: [What failed] ### Context for Debug: - Error messages: [from ReadLints] - Expected behavior: [from QA Contract] - Actual behavior: [observed] Invoking debug skill with context...

After debug fixes, re-run qa-commit to verify.

Integration with Debug

When verdict is RED:

  1. Automatically invoke debug skill
  2. Pass context:
    • Failed G#N or AC#N
    • Error messages from ReadLints/Shell
    • Browser console/network errors (if applicable)
  3. Debug skill fixes issue
  4. Re-run qa-commit
  5. Repeat until GREEN or user intervention

MCP Tools Used

ToolPurpose
ReadLintsGet lint/type errors
ShellRun tests, typecheck
Browser MCPStorybook verification
SemanticSearchFind implementations
GrepSearch for patterns

Invocation

Invoked by:

  • commit.mdc - After pr-review passes
  • agent.mdc - Part of commit-level workflow

Or manually with "use qa-commit skill".

区块链

快捷安装

复制到终端去安装 Skill

npxskillsaddWellApp-ai/Well--skill"qa-commit"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
property-based-testing
通过生成随机输入验证代码在各类边界条件下的行为一致性,适用于序列化、解析、归一化及纯函数等场景,能有效发现隐含缺陷并提升测试覆盖率,尤其适合需要高可靠性的算法与智能合约验证。
compliance-checker
能够对基础设施配置进行合规性评估,检查是否符合 SOC2、HIPAA 和 PCI DSS 等行业标准,识别潜在的安全风险与违规项,并生成改进建议报告,适用于安全审计与合规审查场景。
orchestration
作为系统的核心协调中枢,负责将用户复杂需求拆解为并行任务流,动态调度不同能力的智能体协同工作,自动管理任务依赖与执行状态,并在后台静默完成多线程探索、分析与实现,最终整合结果交付完整解决方案。
skill-adapter
对基础设施配置进行多标准合规性评估,覆盖 SOC2、HIPAA 和 PCI DSS 等主流框架,自动识别配置偏差与安全风险,并生成可操作的整改建议报告,支撑持续合规治理与审计准备。
contract-test-creator
自动生成符合行业规范的契约测试代码与配置,提供从框架搭建到单元测试、集成测试及模拟对象编写的全流程支持,适用于需要实现高质量自动化测试验证的开发场景。