the-scribe

Generate conventional commit messages, PR descriptions, and changelogs from diffs.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/fworks-tech/agenthood --skill the-scribe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-scribe
Source: https://github.com/fworks-tech/agenthood/tree/main/members/the-scribe
Command: npx skills add https://github.com/fworks-tech/agenthood --skill the-scribe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and standardizing messages around code changes is time-consuming and error-prone. This skill automatically converts diffs and branch history into clear commit messages, PR descriptions, and changelogs, helping teams communicate intent and rationale.

Core Features & Use Cases

  • Commit Message Writer: analyzes staged changes and proposes a conventional commit with a concise subject, a meaningful scope, and a detailed rationale.
  • PR Description Writer: generates a one-paragraph summary, a test plan, and a closes footer to link to issues.
  • Changelog Generator: compiles user-facing release notes from commit history, grouping entries by feature, fix, and improvement.

Quick Start

Load this skill into your agent runtime and start generating clear commit messages, PR descriptions, and changelogs from your diffs.

Frequently Asked Questions about the-scribe

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

You can generate a conventional commit message from a git diff by loading this skill into your agent runtime, which analyzes staged changes to propose a concise subject, meaningful scope, and detailed rationale.

What is the best way to automate PR descriptions from branch history?

The best way to automate PR descriptions from branch history is by using this skill to generate a one-paragraph summary, a structured test plan, and a closes footer linking to related issues.

How do I compile user-facing changelogs from commit history?

You can compile user-facing changelogs from commit history by grouping release notes into categories, specifically separating entries by feature, fix, and improvement to communicate intent clearly.

Can I use conventional commits for both single and multiple code changes?

Yes, you can apply conventional commits for both single and multiple code changes across software development workflows, spanning from staging initial changes to preparing final releases.

Does this skill require external dependencies to document the rationale behind code modifications?

No, the skill requires no external dependencies to document the rationale behind code modifications, operating independently within your agent runtime to enforce standard commit structures.