skills.rest
firstaxel
firstaxelCOMMUNITY
Explore all skills by this author →
GitHub

document

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

Updated Feb 27, 2026
Search Tags:#git#changelog#documentation#pull request#technical writing#release notes#postmortem
One-click install
npx skills add https://github.com/firstaxel/neon --skill document-firstaxel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/firstaxel/neon/tree/main/.agents/skills/document
Command: npx skills add https://github.com/firstaxel/neon --skill document-firstaxel

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 PR titles and bodies, Keep a Changelog entries, end-user release notes, and blameless postmortems from one command. - Grounded in the record: Reads the actual branch commits and diff as the source of truth, never inventing features, timelines, or root causes. - GitHub integration: Optionally creates or updates PRs 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 with What, Why, Changes, and test steps, derived from your actual diff. ## Quick Start Ask the agent to run the document skill with the type you need, for example: write a PR description for my current branch using the document skill.

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 my branch commits?▼

Run the document skill with the pr type on a feature branch ahead of its base. It reads the branch commits and diff versus the base branch, then produces a title and structured body covering what, why, changes, and how to test.

How do I write a changelog entry from a merged change?▼

Run the skill with the changelog type. It appends an entry to CHANGELOG.md under the unreleased section, matching the existing file format if one exists, or creating a Keep a Changelog structure for new files.

Can it create or update a GitHub pull request automatically?▼

Yes, when the gh CLI is installed and the repo has a remote. It uses gh pr create for new PRs or gh pr edit for existing ones, but always shows the body and asks for confirmation before running any gh command.

What happens if my repository has no version tags for release notes?▼

The skill detects the missing tags and asks you to provide a version name and commit range, or offers to cover all commits since the first one. It never guesses a range on its own.

Does the postmortem generator invent incident details?▼

No. It builds the postmortem only from incident facts you provide plus any debug records, marking unknowns as "Unknown, to investigate" rather than fabricating timeline entries or root causes.

Related Skills

Explore More Software Engineering Skills→
sarkarshivaditya-labsarkarshivaditya-lab

Git Commit

Generates storytelling-focused Conventional Commits messages with Jira context, then commits and pushes changes.

Community
Intermediate
elie222elie222
12.1k

changelog

Creates user-facing changelog entries and regenerates the aggregated changelog file.

Community
Intermediate
EcoPasteHubEcoPasteHub
7.3k

trellis-check

Verifies code changes against specs, lint, type checks, tests, and cross-layer consistency.

Official
Intermediate
AstrumonAstrumon

changelog-generator

Generate Keep a Changelog entries from Conventional Commits history.

Community
Intermediate