1. Habit
  2. Skills
  3. Document skill
jsmastery-pro · 4K installs

Document skill
Runs by itself, change ready to document.

Every change gets human-facing prose.

Install the Document skill and make it a habit: follow https://gethabit.dev/skills/jsmastery-pro/document.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

4K installs2K starsMIT licenceSource on GitHub ↗

Document

by jsmastery-pro · 4K installs

The skill

Document writes the human-facing prose about a change, a PR description, changelog entry, release note or postmortem, drafting from the real commits and diff and writing to the right place.

Only when you ask.

The habit

Every change gets human-facing prose.

↻ Runs by itselfchange ready to document

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

change ready to document. Runs in Claude Code routine.

  • ↻ change ready to document
  • /document pr or on merge

02

It checks its work

sourced + confirmed. If a check fails, it tells you.

  • ✓every statement traces to a commit, diff or given incident fact
  • ✓the document is written to the right place for its type
  • ✓no gh command or push runs without your confirmation

03

It remembers

commit and diff. The next run reads it first: the branch commits, the diff against base and recent spec paths for the why.

git log

One run, step by step.
Then it stops.

Stop ruleStops after one document per run.

  1. 01

    Pick the type

    Use the given type or infer pr, changelog, release-note or postmortem, confirming with one question.

  2. 02

    Gather the source

    Collect the commit list and diff, and for a postmortem ask you for the incident facts git cannot hold.

  3. 03

    Write the document

    Read the agent prompt and the chosen template and write the document from the real record.

  4. 04

    Match the format

    Match an existing CHANGELOG style and resolve the release range from tags.

  5. 05

    Confirm before gh

    For a PR, show the body and confirm before any gh pr create, edit or push.

  6. 06

    Relay the result

    Report the type, where it landed and the full PR body in chat.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Document skill helps.

Use it when

  • ✓ You need a PR description
  • ✓ You add a changelog or release note
  • ✓ You write a postmortem

Skip it when

  • – You want code or tests written
  • – There is no change to describe

Questions

Document skill, answered.

Does it write code or specs?

No. It writes only the human-facing prose: PR text, changelog, release notes and postmortems.

Will it invent a postmortem timeline?

No. It uses only the incident facts you give and the commits; it never invents a timeline or cause.

How do I install the Document skill?

Copy the prompt at the top into your agent. It installs the skill from jsmastery-pro/skills and sets up the habit. Or run npx skills add jsmastery-pro/skills --skill document.

Is the Document skill free?

Yes. It is published under MIT. Habit is free too.

Document. Now as a habit.

Install the Document skill and make it a habit: follow https://gethabit.dev/skills/jsmastery-pro/document.md

  • Free
  • No account
  • Undo in one line

All jsmastery-pro skills →More docs skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by jsmastery-pro, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.