Skip to content
Agentmart
Submit a tool

document-changes

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

Skill by gregwebs

IndexedMIT★ 20
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gregwebs-document-changes

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Use cases: documents

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/document-changes

What's inside

Skill name
document-changes
Description
Record changes in either a PR, issues, docs, or chat output
License
MIT
Instructions
24 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## 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

From gregwebs/skills-sdlc, MIT.

More from gregwebs/skills-sdlc

Signals

Stars
20
Forks
1
Open issues
1
Last commit (this folder)
Sep 25, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/gregwebs/skills-sdlc
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from gregwebs

Cite this page

document-changes skill. Agent Mart. https://agentmart.dev/skills/gregwebs-document-changes (last updated 2026-10-24)