document

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/JabezJesudasonJena/hack-ag --skill document-jabezjesudasonjena
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/JabezJesudasonJena/hack-ag/tree/main/.agents/skills/document
Command: npx skills add https://github.com/JabezJesudasonJena/hack-ag --skill document-jabezjesudasonjena

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing human-facing documentation about code changes is tedious 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 per version, or produce a blameless postmortem from incident facts. - Grounded in the record: Reads the actual git log and diff as the source of truth, never inventing features, timeline entries, or root causes. - GitHub integration: Optionally creates or updates a PR via the gh CLI after confirmation, with graceful fallback to chat-only output. - Use Case: After finishing a feature branch, run the skill with pr to get a reviewer-ready title and body covering what changed, why, how to verify, and the rollout risk. ## Quick Start Ask the agent to run the document skill with the pr option to draft a PR description from the current branch's 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 skill with the pr argument on a feature branch. It reads the branch commits and diff against the base branch, then produces a title and structured body covering what changed, why, how to test, and rollout risk.

How to write release notes from git tags automatically?

Use the release-note type, which derives the range from the two most recent git tags or a range you provide. It writes user-facing notes to docs/releases/<version>.md, translating technical changes into user benefits.

Can it create or update a GitHub pull request?

Yes, when the gh CLI is installed and the repo has a remote. It creates a PR with gh pr create or updates an existing one with gh pr edit, but only after showing you the body and getting confirmation.

Does the changelog generation match my existing CHANGELOG.md format?

Yes. If CHANGELOG.md exists, it follows the file's established structure and wording style. It only applies the Keep a Changelog format when creating the file fresh, and skips duplicate entries.

What information is needed to write a postmortem?

You provide the incident facts: what broke, when with timezone, user impact, detection method, and root cause or fix. The skill builds a blameless postmortem from those facts and never invents timeline entries or causes.