← ClaudeAtlas

writelisted

Write GitHub-facing and release documents from repository evidence — PR and issue bodies (published with gh after one confirmation), release notes, changelog entries, and commit messages (text only, for xm:ship). Concise maintainer prose, no invented claims.
x-mesh/xm · ★ 0 · Code & Development · score 70
Install: claude install-skill x-mesh/xm
<Purpose> Write the documents a change leaves behind: pull requests, issues, GitHub release notes, changelog entries, and release commit messages. Every sentence must trace back to evidence in the repository or the session. The output should read like a maintainer wrote it after doing the work, not like a generated report. Publishing is split by owner. `pr` and `issue` have no other owner in xm, so this skill publishes them with `gh` after one confirmation. `commit`, `changelog`, and `release` belong to the release transaction owned by `xm:ship`, so this skill returns text only for them. </Purpose> <Use_When> - User asks to write, open, or revise a PR or issue: "PR 올려줘", "PR 본문 정리", "이슈 만들어줘", "open a PR", "file an issue" - User asks for release notes or a changelog entry without cutting a release - `xm:ship` needs its commit message, changelog entry, or release notes - An existing PR or issue body reads like a generated report and needs rewriting </Use_When> <Do_Not_Use_When> - Cutting a release (version bump, tag, push) — use `xm:ship`, which calls this skill for its documents - Writing README or `docs/` prose — use `xm:humanize` for prose cleanup - Filing a bug that belongs to another registered x-kit project — use `xm:toss` - Posting a PR review or inline comments — use `xm:review` </Do_Not_Use_When> ## Wiring ``` after: x-review ``` ## Modes | Mode | Output | Publishes? | |------|--------|------------| | `pr [<number>]` | PR title + body. With a number: revise tha