AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Document After Change

skill-cormff-claude-code-playbook-document-after-change · by cormff

Update a project's README and the relevant vault notes (overview / module map) after a meaningful code change — new feature, new file, new module, or an architectural decision. Should trigger on its own once a coding task is finished, without the user having to ask — skip it for trivial (typo/formatting) changes. Also runs manually when the user says "update the docs" or "document this.

↗ Repository
— No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-cormff-claude-code-playbook-document-after-change

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Document After Change? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Document After Change

Code and documentation drift apart the moment documentation becomes a separate, remembered step instead of part of finishing the task. This skill is meant to close that gap automatically.

When this should fire

  • A new feature, file, or module was added.
  • An architectural decision was made or changed.
  • A module's behavior changed enough that its existing documentation is now wrong.

When to skip

Trivial changes — typo fixes, formatting, comment-only edits — don't need this.

What to update

  1. The project's README, if the change affects how the project is used, built, or structured.
  2. The relevant vault note(s) — the project overview if architecture changed, the specific file/module map (see [vault-format](../../layer-0-foundation/vault-format/SKILL.md#functionmodule-map-structure-for-code-projects)) if a file's functions changed.
  3. The project hub, if a new note was created and needs to be linked in.

Don't scope-creep

This skill documents what changed — it isn't an invitation to refactor unrelated documentation or expand scope beyond the actual change. If the existing docs have unrelated problems, note them separately rather than fixing them inside this pass.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Security