document

Generate PR descriptions, changelogs, release notes, and postmortems from git history.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/idehen-divine/lumished --skill document-idehen-divine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/idehen-divine/lumished/tree/main/.ai/skills/document
Command: npx skills add https://github.com/idehen-divine/lumished --skill document-idehen-divine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing human facing documentation about code changes is slow and often skipped. This Skill drafts PR descriptions, changelog entries, release notes, and incident postmortems directly from the real commits and diffs, so every claim is grounded in what actually changed. ## Core Features & Use Cases - Four document types: Generate a PR title and body, append a Keep a Changelog entry, write end user release notes to docs/releases/, or produce a blameless postmortem in docs/postmortems/. - Grounded in git history: Reads branch commits, diffs, tags, and recent specs so the prose reflects the actual change rather than invented claims. - GitHub CLI integration: Detects gh availability, remotes, and existing PRs to optionally create or update the pull request body via gh pr create or gh pr edit. - Use Case: After finishing a feature branch, run the document skill with the pr type to get a reviewer ready title and body with What, Why, Changes, test steps, and risk notes, then update the PR with one command. ## Quick Start Ask the agent to run the document skill with the pr type to draft a pull request description from the current branch commits and diff.

Frequently Asked Questions about document

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a PR description from git commits?▼

Run the document skill with the pr type. It collects branch commits and the diff against the base branch, then writes a title and body with What, Why, Changes, test steps, and risk notes, optionally creating or updating the PR via the gh CLI.

How to write a changelog entry automatically from a diff?▼

Use the changelog type. The skill reads the merged change set, matches the existing CHANGELOG.md format if present, and appends categorized entries under the Unreleased section without duplicating existing lines.

Can it create a GitHub pull request directly?▼

Yes, when the gh CLI is installed and the repo has a remote. If a PR already exists it runs gh pr edit to update the body, otherwise gh pr create. Without gh or a remote, the PR text is shown in chat only.

Does the document skill write code or tests?▼

No. It only writes prose artifacts: PR text, CHANGELOG.md, docs/releases/, and docs/postmortems/. It does not commit, push, merge, or modify source code, tests, or specs.

What happens when a repo has no version tags for release notes?▼

The skill asks for a version name and commit range instead of guessing. You can provide a range like v1.0.0 covering specific commits, or let it cover all commits since the first one.

How does the postmortem type get incident details?▼

Git history lacks incident narratives, so the skill asks the engineer for what broke, when, user impact, detection method, and root cause. It never fabricates timeline entries and marks unknowns as to investigate.