skill-review
Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 2.5k
- Forks
- 205
01 前言 Front Matter
- name
- skill-review
- description
- Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.
02 资源文件 3
- 参考文档references/audit-checklist.md2.0 KB
- 参考文档references/inspection-commands.md341 B
- 参考文档references/reference-patterns.md3.5 KB
03 SKILL.md 正文
Skill Review
Review a skill as an execution contract, not as prose. Trace how an agent would enter, load, delegate, produce artifacts, and verify results; then report the smallest changes that would improve that chain.
Review Workflow
- Resolve the target skill or prompt chain. If the user names a path, stay on that path and its directly linked resources.
- Read repo instructions first: nearest
AGENTS.md, plugin manifests, and the targetSKILL.mdfrontmatter/body. - Trace the chain from entrypoint to references, templates, scripts, detectors, tests, generated artifacts, and validation commands. Build an ownership map: what file owns workflow, output structure, runtime rules, style, and tests.
- Audit the contract before editing. Use Audit Checklist and Reference Patterns as lenses.
- If the user asked for changes, patch only the smallest owning files. Keep
generated helpers, smoke scripts, and local experiments outside
SKILL.mdunless they are durable resources the skill must use. - Validate with the lightest real gate available: skill validator, repo tests, plugin validation, or a bounded agent smoke. State any gate that could not be run.
Use subagents only as an evaluation surface or for independent broad research. The lead agent owns the review, final calibration, and file edits. Pass raw artifacts and task-local scope to subagents; do not pass the intended answer.
Review Lenses
- Audit Checklist: trigger contract, progressive disclosure, workflow/delegation, template ownership, readability, evidence.
- Reference Patterns: reusable design lenses such as Trigger/Protocol split, Gate Function, and Output Contract Slots.
- Fast Inspection Commands: starting
rg,wc, andgit diff --checkprobes adapted to the repo.
Finding Severity
- P0: The skill points to missing, empty, contradictory, or invalid resources; an agent can follow the instructions and fail.
- P1: The skill works but wastes context, duplicates ownership, hides key constraints, or produces unreadable output.
- P2: Style, naming, wording, or organization issues that reduce scanability without breaking the workflow.
Report Shape
Lead with findings, ordered by severity. Keep each finding concrete:
P1 - <short title>
File: <path>:<line>
Why it matters: <execution or output risk>
Evidence: <quoted phrase, command result, or linked resource>
Fix: <smallest owning-file change>
Validation: <command or smoke that should prove it>
After findings, add open questions only when they block a safe change. If the user asked for edits, include changed files and validation results after the findings. Default to the user's language.
04 同仓库更多 Skills
verify
Verify one bounded change.
handoff
Prepare a bounded handoff.
intent-correlation-analysis
Analyze a bounded IntentCorrelationPacketV1 and propose reviewable links among user inputs, execution slices, change units, commits, artifacts, and validation outcomes. Use when reconstructing why an observed coding-agent change exists or when Studio needs evidence-backed Intent correlation. Do not use for raw transcript summaries, deterministic file-operation collection, or autonomous confirmation of inferred Intent.
better-harness
Use when /better-harness reviews the outer coding-agent Harness for lifecycle controls, repeated work, project feedback, agent assets, session outcomes, repair planning, durable reports, finding-bound fixes, or manual direct fixes. Invoke only via slash command.
generate-harness-dsl
Generate, revise, or review complete Harness as Code `.harness` files when a coding-agent workflow, agent role, skill, tool contract, MCP connection, runtime, or deployment must be compiler-valid and resolvable with `@qoder-ai/harness`.
memory-recap
Create evidence-linked work profiles, diagnose Coding Agent collaboration friction, and recommend concrete improvements from native memories or frozen exports. Use for memory recaps and agent-usage retrospectives, not memory maintenance or session-performance measurement.