ワンクリックで
spec-lint-fix
Run markdown linting from tools/spec-lint/, fix issues, and rerun until clean
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Run markdown linting from tools/spec-lint/, fix issues, and rerun until clean
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | spec-lint-fix |
| description | Run markdown linting from tools/spec-lint/, fix issues, and rerun until clean |
This skill enforces markdown quality after repository changes.
It runs the repository linter from tools/spec-lint/, fixes reported issues in markdown files, and repeats until bash lint.sh exits clean.
AGENTS.md at the repository root.bash lint.sh in tools/spec-lint/.Repeat the following loop until lint passes:
bash lint.sh in tools/spec-lint/.tools/spec-lint/ only.bash lint.sh exactly (do not substitute another command).AGENTS.md intact.Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: writes a ranked checklist to plans/AUDIT.md of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", or calls ponytail-audit. One-shot report, does not apply fixes.
Fix ponytail audit items from plans/AUDIT.md one at a time. For each item: implementer fix → ponytail-review → normal review → quality gate → mark done → commit. Cycle until reviewer is happy at each stage. Complements ponytail-audit.
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or calls ponytail-review. Complements the correctness-focused reviewer subagent — this one only hunts complexity.
Use when executing a project folder under plans/ that contains SPEC.md, PLAN.md, and PHASE_XX.md files.
Fix the first incomplete checklist item in plans/<project>/REVIEW.md, commit the fix, then stop. Does not commit REVIEW.md — it is gitignored by design.
Review the current repository state against a project's SPEC.md in plans/<project-name>/ and produce a checklist of issues in REVIEW.md. Use when you need a methodical spec-compliance audit of the present codebase.