agentleFS
Sign inStart free
gregwebsgregwebs/skills-sdlc/skills/document-changes/SKILL.md

document-changes

Skill20 starsChanged 43 days agoMITView on GitHub

Record changes in either a PR, issues, docs, or chat output

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If an implementation plan is available, that should have all the detail needed.

    line 14
  2. Distinctive:

    Use the /explain-changes skill to explain the changes, but omit the quiz.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Change Record

A Change Record captures an ephemeral implementation moment; it is not lasting technical documentation.

The ticket or spec has information that should be included or referenced (if linked) for high-level information.

A change record should have some additional implementation detail. If an implementation plan is available, that should have all the detail needed.

Use the /explain-changes skill to explain the changes, but omit the quiz. Include technical decisions, completed checklist items, and the verifications performed.

Capture follow-on information that would help the next related change.

Record a change record in 1 location prioritized according to this order:

  • The PR when one is authorized.
  • On the issue when an issue tracker is configured
  • in an applicable local issue file if local issue files are used
  • in an applicable local documentation folder if one is in use
  • in the commit message
  • in the final chat output when no durable location exists

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free