メニュー
Same-commit doc edit discipline for fleet-generator — every behavior-changing mission ships its doc update in the same commit series as the code change.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/bob-codedaptive/fleet-generator --skill documentation-revコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | documentation-rev |
| description | Same-commit doc edit discipline for fleet-generator — every behavior-changing mission ships its doc update in the same commit series as the code change. |
| when_to_use | Authoring or revising a documentation file. Reviewing whether a behavior-changing mission shipped its doc edit. Bumping a doc's version. Trigger phrases: documentation rev, doc revision, same-commit doc edit, rev bump, README update, behavior-changing mission. |
| status | active |
| tags | ["skill"] |
| updated | 2026-05-07T00:00:00.000Z |
Every behavior-changing mission ships its doc update in the same commit series as the code that changes the behavior. Forward-only. No deltas.
A behavior-changing mission must include a doc edit in the same commit series. Concretely:
A code commit without the corresponding doc edit is rejected at post-flight and bounced back to the worker.
What does NOT count:
"Same commit" means the doc edit is in the same Part as the code change. Not "I'll do docs at the end" — that's how docs lag behind shipped behavior, then drift, then become wrong.
If the mission has 4 Parts, and Part 2 changes user-visible behavior, the doc edit is in Part 2's commit. Not Part 5.
For docs that carry version numbers (API references, schema docs):
| Change | Version bump |
|---|---|
| Typo, wording cleanup | No bump; update updated: if frontmatter has it |
| Add a rule, field, or setting | Patch bump (v1.2 → v1.2.1) |
| Multi-section rewrite | Minor bump (v1.2 → v1.3) |
| Structural change | Major bump (v1.2 → v2.0) |
See references/version-bumping.md for examples.
Architecture Decision Records: written once, never re-opened.
Statuses: proposed, accepted, rejected, superseded.
Once accepted, the text doesn't change. Errors get corrected by a
new ADR that supersedes the old one.
Garfield verifies in post-flight that any behavior-changing mission shipped a corresponding doc edit. Missing doc edit → CRITICAL finding → merge blocked.
