ln-510-quality-coordinator by levnikolaevich/claude-code-skills
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-510-quality-coordinator路径说明: 文件路径(
shared/、references/、../ln-*)是相对于技能仓库根目录的。如果在当前工作目录未找到,请定位此 SKILL.md 文件所在的目录,然后向上移动一级以找到仓库根目录。如果缺少shared/目录,请通过 WebFetch 从https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}获取文件。
用于代码质量管道的顺序协调器。调用工作器(ln-511 → ln-512 → ln-513 → ln-514),与第 5-8 阶段并行运行内联代理审查,合并所有结果,并返回质量裁决。
| 输入 | 必需 | 来源 | 描述 |
|---|---|---|---|
storyId |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 是 |
| args, git branch, kanban, user |
| 要处理的需求 |
解析: 需求解析链。状态过滤器: 待审查
references/gate_levels.md 计算质量裁决必读: 加载 shared/references/input_resolution_pattern.md
docs/tasks/kanban_board.md 自动发现团队/配置changed_files[]):必读: 加载 shared/references/git_scope_detection.md 根据指南运行算法 → 构建 changed_files[]快速通道模式: 当使用 --fast-track 标志调用时(准备度 10/10),运行阶段 2 时使用 --skip-mcp-ref(仅指标 + 静态分析,无 MCP 参考),跳过阶段 3(ln-512),运行阶段 4 时使用至少 1 个代理(从 2 个减少)。运行阶段 5(标准)、阶段 6(代码检查工具)、阶段 7(ln-513)、阶段 8(ln-514)。
强制步骤: 在所有模式下都必须调用 ln-511。完整关卡: ln-511 运行所有内容(指标 + MCP 参考 + 静态分析)。快速通道: ln-511 运行
--skip-mcp-ref(仅指标 + 静态分析 — 无需昂贵的 MCP 参考调用即可捕获复杂度、DRY、死代码)。
调用方式:
# 完整关卡:
Skill(skill: "ln-511-code-quality-checker", args: "{storyId}")
# 快速通道:
Skill(skill: "ln-511-code-quality-checker", args: "{storyId} --skip-mcp-ref")
强制步骤(完整关卡): 必须调用 ln-512。仅进行安全的自动修复(置信度 >=90%)。快速通道: 跳过此阶段。
调用方式:
Skill(skill: "ln-512-tech-debt-cleaner", args: "{storyId}")
强制步骤: 在后台启动代理,结果在阶段 9 合并。快速通道: 仅启动 1 个代理(最可用的)。结果在阶段 9 正常合并。
必读: 加载 shared/references/agent_review_workflow.md、shared/references/agent_delegation_pattern.md
4a) 健康检查(根据共享工作流程“步骤:健康检查”): - 读取 docs/environment_state.json → 排除 disabled: true 的代理 - 为剩余代理运行 node shared/agents/agent_runner.mjs --health-check - 如果 0 个代理可用 → 代理审查被跳过,进入阶段 5 4b) 获取参考: get_issue(storyId) + list_issues(parent=storyId, status=Done)(排除测试任务) 4c) 构建提示: 从 shared/agents/prompt_templates/review_base.md + modes/code.md 组装(根据共享工作流程“步骤:构建提示”),替换 {story_ref}、{task_refs}。保存到 .agent-review/{identifier}_codereview_prompt.md 4d) 启动两个代理作为后台任务。agents_launched = true 精确命令(根据 agent_delegation_pattern.md): node shared/agents/agent_runner.mjs --agent {name} --prompt-file .agent-review/{agent}/{id}_codereview_prompt.md --output-file .agent-review/{agent}/{id}_codereview_result.md --cwd {project_dir} → 继续阶段 5(标准验证)、阶段 6(代码检查工具)、阶段 7(回归测试)、阶段 8(日志分析),同时代理在工作
必读: 加载 references/criteria_validation.md
| 检查项 | 描述 | 失败操作 |
|---|---|---|
| #1 需求依赖关系 | 史诗内无前向依赖 | [DEP-] 问题 |
| #2 验收标准-任务覆盖度 | 强/弱/缺失评分 | [COV-]/[BUG-] 问题 |
| #3 数据库创建原则 | 模式范围与需求匹配 | [DB-] 问题 |
必读: shared/references/ci_tool_detection.md(发现层次结构 + 命令注册表)
调用方式:
Skill(skill: "ln-513-regression-checker", args: "{storyId}")
调用方式:
Skill(skill: "ln-514-test-log-analyzer", args: "review logs since test run start, expected errors from negative test cases")
必读: 加载 shared/references/agent_review_workflow.md(关键验证 + 迭代优化)、shared/references/agent_review_memory.md
9a) 等待代理结果 — 在结果文件到达时读取(按到达处理模式) 9b) 关键验证 根据共享工作流程 — Claude 根据优点评估每条建议 9c) 将接受的建议合并到问题列表中(SEC-、PERF-、MNT-、ARCH-、BP-、OPT-) - 如果 area=security 或 area=correctness → 将聚合问题升级为关注 9d) 将审查摘要保存到 .agent-review/review_history.md
协议规则: 有效跳过条件:(1) 在阶段 4 健康检查中 Codex 不可用,(2) 代理被跳过。如果跳过 → 记录
"迭代优化:已跳过"。
根据 shared/references/agent_review_workflow.md “步骤:迭代优化”执行。
"迭代优化:{N} 次迭代,{total} 条建议,{applied} 条已应用,退出原因:{reason}".agent-review/refinement/,追加到 review_history.md必读: 加载 references/gate_levels.md
使用此矩阵将每个组件状态映射到失败/关注/忽略:
| 组件 | 状态 | 映射到 | 罚分 |
|---|---|---|---|
| quality_check | 通过 | -- | 0 |
| quality_check | 关注 | 关注 | -10 |
| quality_check | 发现问题 | 失败 | -20 |
| criteria_validation | 通过 | -- | 0 |
| criteria_validation | 关注 | 关注 | -10 |
| criteria_validation | 失败 | 失败 | -20 |
| linters | 通过 | -- | 0 |
| linters | 失败 | 失败 | -20 |
| regression | 通过 | -- | 0 |
| regression | 失败 | 失败 | -20 |
| tech_debt_cleanup | 已清理 | -- | 0 |
| tech_debt_cleanup | 无需清理 | -- | 0 |
| tech_debt_cleanup | 构建失败 | 失败 | -20 |
| tech_debt_cleanup | 已跳过 | 忽略 | 0 |
| agent_review | 代码可接受 | -- | 0 |
| agent_review | 建议(安全/正确性) | 关注 | -10 |
| agent_review | 已跳过 | 忽略 | 0 |
| log_analysis | 干净 | -- | 0 |
| log_analysis | 仅警告 | -- | 0 |
| log_analysis | 发现真实错误 | 失败 | -20 |
| log_analysis | 已跳过 / 无日志源 | 忽略 | 0 |
fail_count = 映射到失败的组件数量
concern_count = 映射到关注的组件数量
quality_score = 100 - (20 * fail_count) - (10 * concern_count)
# 快速失败覆盖:任何失败 -> 无论分数如何,裁决为失败
IF fail_count > 0:
quality_verdict = 失败
ELSE IF quality_score >= 90:
quality_verdict = 通过
ELSE IF quality_score >= 70:
quality_verdict = 关注
ELSE:
quality_verdict = 失败
quality_verdict: 通过 | 关注 | 失败
quality_score: {0-100}
fail_count: {N}
concern_count: {N}
ignored_components: [tech_debt_cleanup, agent_review] # 仅在已跳过时
quality_check: 通过 | 关注 | 发现问题
code_quality_score: {0-100}
agent_review: 代码可接受 | 建议 | 已跳过
criteria_validation: 通过 | 关注 | 失败
linters: 通过 | 失败
tech_debt_cleanup: 已清理 | 无需清理 | 构建失败 | 已跳过
regression: 通过 | 失败
log_analysis: 干净 | 仅警告 | 发现真实错误 | 已跳过
issues:
- {id: "SEC-001", severity: high, finding: "...", source: "ln-511"}
- {id: "OPT-001", severity: medium, finding: "...", source: "agent-review"}
- {id: "DEP-001", severity: medium, finding: "...", source: "criteria"}
- {id: "LINT-001", severity: low, finding: "...", source: "linters"}
TodoWrite 格式(强制):
- 调用 ln-511-code-quality-checker (进行中)
- 调用 ln-512-tech-debt-cleaner (待定)
- 启动代理审查(后台)(待定)
- 标准验证(需求依赖、验收标准覆盖度、数据库模式)(待定)
- 运行 tech_stack.md 中的代码检查工具 (待定)
- 调用 ln-513-regression-checker (待定)
- 调用 ln-514-test-log-analyzer (待定)
- 合并代理审查结果 (待定)
- 计算质量裁决 + 返回结果 (待定)
| 阶段 | 工作器 | 上下文 |
|---|---|---|
| 2 | ln-511-code-quality-checker | 共享(技能工具)— 代码指标、MCP 参考、静态分析 |
| 3 | ln-512-tech-debt-cleaner | 共享(技能工具)— 自动修复来自 ln-511 的安全发现项 |
| 4 | 内联代理审查(Codex + Gemini) | 后台 — 在 ln-512 后启动,在阶段 9 合并 |
| 7 | ln-513-regression-checker | 共享(技能工具)— 所有变更后的完整测试套件 |
| 8 | ln-514-test-log-analyzer | 共享(技能工具)— 错误分类 + ln-513 后的日志质量 |
所有工作器: 通过技能工具调用 — 工作器可以看到协调器上下文。代理审查内联运行(无技能委托)。
反模式:
--skip-mcp-ref),返回代码质量分数必读: 加载 shared/references/meta_analysis_protocol.md
技能类型:review-coordinator(带代理)。在所有阶段完成后运行。使用 review-coordinator — with agents 格式输出到聊天。
references/criteria_validation.mdreferences/gate_levels.md../ln-511-code-quality-checker/SKILL.md、../ln-512-tech-debt-cleaner/SKILL.md、../ln-513-regression-checker/SKILL.md、../ln-514-test-log-analyzer/SKILL.mdshared/references/agent_review_workflow.mdshared/references/agent_delegation_pattern.mdshared/references/agent_review_memory.mdshared/agents/prompt_templates/review_base.md + modes/code.md../ln-500-story-quality-gate/SKILL.md../ln-520-test-planner/SKILL.mddocs/project/tech_stack.md版本: 7.0.0 最后更新: 2026-02-09
每周安装次数
129
仓库
GitHub 星标数
245
首次出现
2026年2月11日
安全审计
安装于
cursor121
opencode121
gemini-cli120
codex120
github-copilot120
claude-code120
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. Ifshared/is missing, fetch files via WebFetch fromhttps://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.
Sequential coordinator for code quality pipeline. Invokes workers (ln-511 → ln-512 → ln-513 → ln-514), runs inline agent review in parallel with Phases 5-8, merges all results, and returns quality_verdict.
| Input | Required | Source | Description |
|---|---|---|---|
storyId | Yes | args, git branch, kanban, user | Story to process |
Resolution: Story Resolution Chain. Status filter: To Review
references/gate_levels.mdMANDATORY READ: Load shared/references/input_resolution_pattern.md
docs/tasks/kanban_board.mdchanged_files[] for ln-511 via coordinator context): MANDATORY READ: Load shared/references/git_scope_detection.md Run algorithm from guide → build changed_files[]Fast-track mode: When invoked with --fast-track flag (readiness 10/10), run Phase 2 with --skip-mcp-ref (metrics + static only, no MCP Ref), skip Phase 3 (ln-512), run Phase 4 with 1 agent minimum (reduced from 2). Run Phase 5 (criteria), Phase 6 (linters), Phase 7 (ln-513), Phase 8 (ln-514).
MANDATORY STEP: ln-511 invocation required in ALL modes. Full gate: ln-511 runs everything (metrics + MCP Ref + static analysis). Fast-track: ln-511 runs with
--skip-mcp-ref(metrics + static analysis only — catches complexity, DRY, dead code without expensive MCP Ref calls).
Invocation:
# Full gate:
Skill(skill: "ln-511-code-quality-checker", args: "{storyId}")
# Fast-track:
Skill(skill: "ln-511-code-quality-checker", args: "{storyId} --skip-mcp-ref")
MANDATORY STEP (full gate): ln-512 invocation required. Safe auto-fixes only (confidence >=90%). Fast-track: SKIP this phase.
Invocation:
Skill(skill: "ln-512-tech-debt-cleaner", args: "{storyId}")
MANDATORY STEP: Launches agents in background, results merged in Phase 9. Fast-track: Launch 1 agent only (most available). Results merged in Phase 9 as normal.
MANDATORY READ: Load shared/references/agent_review_workflow.md, shared/references/agent_delegation_pattern.md
4a) Health Check (per shared workflow "Step: Health Check"): - Read docs/environment_state.json → exclude agents with disabled: true - Run node shared/agents/agent_runner.mjs --health-check for remaining agents - If 0 agents → agent review SKIPPED, go to Phase 5 4b) Get references: get_issue(storyId) + list_issues(parent=storyId, status=Done) (exclude test tasks) 4c) Build prompt: Assemble from shared/agents/prompt_templates/review_base.md + modes/code.md (per shared workflow "Step: Build Prompt"), replace {story_ref}, {task_refs}. Save to 4d) as background tasks. → Continue to Phase 5 (Criteria Validation), Phase 6 (Linters), Phase 7 (Regression), Phase 8 (Log Analysis) while agents work
MANDATORY READ: Load references/criteria_validation.md
| Check | Description | Fail Action |
|---|---|---|
| #1 Story Dependencies | No forward deps within Epic | [DEP-] issue |
| #2 AC-Task Coverage | STRONG/WEAK/MISSING scoring | [COV-]/[BUG-] issue |
| #3 DB Creation Principle | Schema scope matches Story | [DB-] issue |
MANDATORY READ: shared/references/ci_tool_detection.md (Discovery Hierarchy + Command Registry)
Invocation:
Skill(skill: "ln-513-regression-checker", args: "{storyId}")
Invocation:
Skill(skill: "ln-514-test-log-analyzer", args: "review logs since test run start, expected errors from negative test cases")
MANDATORY READ: Load shared/references/agent_review_workflow.md (Critical Verification + Iterative Refinement), shared/references/agent_review_memory.md
9a) Wait for agent results — read result files as they arrive (process-as-arrive pattern) 9b) Critical Verification per shared workflow — Claude evaluates each suggestion on merits 9c) Merge accepted suggestions into issues list (SEC-, PERF-, MNT-, ARCH-, BP-, OPT-) - If area=security or area=correctness → escalate aggregate to CONCERNS 9d) Save review summary to .agent-review/review_history.md
PROTOCOL RULE: Valid skip: (1) Codex unavailable in Phase 4 health check, (2) agents SKIPPED. If skipped → log
"Iterative Refinement: SKIPPED".
Execute per shared/references/agent_review_workflow.md "Step: Iterative Refinement".
"Iterative Refinement: {N} iterations, {total} suggestions, {applied} applied, exit: {reason}".agent-review/refinement/, append to review_history.mdMANDATORY READ: Load references/gate_levels.md
Map each component status to FAIL/CONCERN/ignored using this matrix:
| Component | Status | Maps To | Penalty |
|---|---|---|---|
| quality_check | PASS | -- | 0 |
| quality_check | CONCERNS | CONCERN | -10 |
| quality_check | ISSUES_FOUND | FAIL | -20 |
| criteria_validation | PASS | -- | 0 |
| criteria_validation | CONCERNS | CONCERN | -10 |
| criteria_validation | FAIL | FAIL | -20 |
| linters | PASS | -- | 0 |
| linters | FAIL |
fail_count = count of components mapped to FAIL
concern_count = count of components mapped to CONCERN
quality_score = 100 - (20 * fail_count) - (10 * concern_count)
# Fast-fail override: any FAIL -> verdict is FAIL regardless of score
IF fail_count > 0:
quality_verdict = FAIL
ELSE IF quality_score >= 90:
quality_verdict = PASS
ELSE IF quality_score >= 70:
quality_verdict = CONCERNS
ELSE:
quality_verdict = FAIL
quality_verdict: PASS | CONCERNS | FAIL
quality_score: {0-100}
fail_count: {N}
concern_count: {N}
ignored_components: [tech_debt_cleanup, agent_review] # only if SKIPPED
quality_check: PASS | CONCERNS | ISSUES_FOUND
code_quality_score: {0-100}
agent_review: CODE_ACCEPTABLE | SUGGESTIONS | SKIPPED
criteria_validation: PASS | CONCERNS | FAIL
linters: PASS | FAIL
tech_debt_cleanup: CLEANED | NOTHING_TO_CLEAN | BUILD_FAILED | SKIPPED
regression: PASS | FAIL
log_analysis: CLEAN | WARNINGS_ONLY | REAL_BUGS_FOUND | SKIPPED
issues:
- {id: "SEC-001", severity: high, finding: "...", source: "ln-511"}
- {id: "OPT-001", severity: medium, finding: "...", source: "agent-review"}
- {id: "DEP-001", severity: medium, finding: "...", source: "criteria"}
- {id: "LINT-001", severity: low, finding: "...", source: "linters"}
TodoWrite format (mandatory):
- Invoke ln-511-code-quality-checker (in_progress)
- Invoke ln-512-tech-debt-cleaner (pending)
- Launch agent review (background) (pending)
- Criteria Validation (Story deps, AC coverage, DB schema) (pending)
- Run linters from tech_stack.md (pending)
- Invoke ln-513-regression-checker (pending)
- Invoke ln-514-test-log-analyzer (pending)
- Merge agent review results (pending)
- Calculate quality_verdict + return results (pending)
| Phase | Worker | Context |
|---|---|---|
| 2 | ln-511-code-quality-checker | Shared (Skill tool) — code metrics, MCP Ref, static analysis |
| 3 | ln-512-tech-debt-cleaner | Shared (Skill tool) — auto-fix safe findings from ln-511 |
| 4 | Inline agent review (Codex + Gemini) | Background — launched after ln-512, merged in Phase 9 |
| 7 | ln-513-regression-checker | Shared (Skill tool) — full test suite after all changes |
| 8 | ln-514-test-log-analyzer | Shared (Skill tool) — error classification + log quality after ln-513 |
All workers: Invoke via Skill tool — workers see coordinator context. Agent review runs inline (no Skill delegation).
Anti-Patterns:
--skip-mcp-ref in fast-track), code quality score returnedMANDATORY READ: Load shared/references/meta_analysis_protocol.md
Skill type: review-coordinator (with agents). Run after all phases complete. Output to chat using the review-coordinator — with agents format.
references/criteria_validation.mdreferences/gate_levels.md../ln-511-code-quality-checker/SKILL.md, ../ln-512-tech-debt-cleaner/SKILL.md, ../ln-513-regression-checker/SKILL.md, ../ln-514-test-log-analyzer/SKILL.mdshared/references/agent_review_workflow.mdshared/references/agent_delegation_pattern.mdshared/references/agent_review_memory.mdVersion: 7.0.0 Last Updated: 2026-02-09
Weekly Installs
129
Repository
GitHub Stars
245
First Seen
Feb 11, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
cursor121
opencode121
gemini-cli120
codex120
github-copilot120
claude-code120
Skills CLI 使用指南:AI Agent 技能包管理器安装与管理教程
36,300 周安装
CSV数据处理专家 - 大型文件清洗转换、性能优化与SQL查询工具
174 周安装
Stripe订阅系统集成指南:Next.js全栈方案,含计费门户与功能开关
160 周安装
PubChem 数据库 Python 使用指南:化学结构搜索、性质检索与生物活性数据分析
190 周安装
HQQ 半二次量化:无需校准的快速模型量化,支持 8/4/3/2/1 比特精度
189 周安装
iOS构建失败修复指南:Xcode环境、SPM依赖与性能优化解决方案
174 周安装
SimPO 偏好优化教程:无需参考模型,性能优于 DPO,快速训练 Mistral/Llama 模型
189 周安装
.agent-review/{identifier}_codereview_prompt.mdagents_launched = truenode shared/agents/agent_runner.mjs --agent {name} --prompt-file .agent-review/{agent}/{id}_codereview_prompt.md --output-file .agent-review/{agent}/{id}_codereview_result.md --cwd {project_dir}| FAIL |
| -20 |
| regression | PASS | -- | 0 |
| regression | FAIL | FAIL | -20 |
| tech_debt_cleanup | CLEANED | -- | 0 |
| tech_debt_cleanup | NOTHING_TO_CLEAN | -- | 0 |
| tech_debt_cleanup | BUILD_FAILED | FAIL | -20 |
| tech_debt_cleanup | SKIPPED | ignored | 0 |
| agent_review | CODE_ACCEPTABLE | -- | 0 |
| agent_review | SUGGESTIONS (security/correctness) | CONCERN | -10 |
| agent_review | SKIPPED | ignored | 0 |
| log_analysis | CLEAN | -- | 0 |
| log_analysis | WARNINGS_ONLY | -- | 0 |
| log_analysis | REAL_BUGS_FOUND | FAIL | -20 |
| log_analysis | SKIPPED / NO_LOG_SOURCES | ignored | 0 |
shared/agents/prompt_templates/review_base.md + modes/code.md../ln-500-story-quality-gate/SKILL.md../ln-520-test-planner/SKILL.mddocs/project/tech_stack.md