Conventional Commit & PR Description Writer

    2

    Generate evidence-based Conventional Commits and professional PR descriptions from Git diffs and notes.

    Free

    2 usesSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Conventional Commit & PR Description Writer

    Example session with this skill installed

    Generate a PR for this diff: modified auth.ts to add JWT rotation, updated readme.md, and added a test case in auth.test.ts. No breaking changes. Ran unit tests locally.

    • Read your context and instructions
    • Compiled the conventional commit

    I have generated a PR description and Conventional Commit based on your changes to the authentication logic and documentation.

    Conventional Commit

    feat(auth): add JWT rotation and update documentation

    Type: feat
    Scope: auth
    Selection Logic: Introduces a new user-facing capability (JWT rotation) evidenced by auth.ts changes.
    Evidence: auth.ts (logic), auth.test.ts (verification), readme.md (docs).

    Pull Request: Add JWT Rotation Support

    Summary

    This PR implements JSON Web Token (JWT) rotation within the authentication module to improve session security and longevity.

    What Changed

    • Added token rotation logic in auth.ts.
    • Integrated a new test suite in auth.test.ts covering rotation cycles.
    • Updated readme.md with configuration details for the new rotation settings.

    Why

    Reason: Not evidenced in supplied context. (Assumed security hardening).

    Testing

    • Confirmed: Unit tests were executed locally by the developer.

    Breaking Changes

    Breaking changes: None evidenced from the supplied changes.

    Risks / Review Notes

    Ensure the readme.md updates correctly reflect the new environment variables required for rotation intervals.

    Next steps

    1. Copy the Conventional Commit message for your final squash/merge.
    2. Paste the PR description into your version control provider.
    3. Link the specific issue number if applicable.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Writing pull request descriptions and commit messages is a manual bottleneck that leads to vague histories and missed context. Developers often struggle to maintain Conventional Commit standards or accidentally include unsupported claims about testing and implementation.

    What it does Generates strict Conventional Commit messages based on actual Git diffs and developer notes. Drafts professional PR descriptions with clear summaries, change logs, and risk assessments. Audits existing PRs and commits for compliance, accuracy, and unsupported claims. Proposes logical commit boundaries for large, multi-file changesets to maintain a clean history. Categorizes evidence into Confirmed, Inferred, and Not Evidenced to prevent hallucinated details. Why this beats prompting it yourself

    Generic prompts often hallucinate test results or incorrectly classify simple maintenance changes as feat. This skill uses an evidence-first engine that explicitly labels missing context and enforces imperative-style wording, helping keep your Git history high-signal and audit-ready without manual editing.

    Use cases Generating a PR description from a messy diff and a short line of developer notes. Standardizing a team's commit history to follow the Conventional Commits specification. Breaking down a large feature branch into a logical sequence of atomic commits. Validating that a PR title accurately reflects the actual code changes before merging. Known limitations

    Requires a Git diff, file list, or developer notes to function. It cannot inspect your local repository or run tests to verify results.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    Requires manual input of diffs or notes. Cannot access local git internals or execute tests to verify code behavior.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    2 uses

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill analyzes your Git diffs and developer notes to generate professional PR descriptions and Conventional Commits, solving the problem of vague histories and 'hallucinated' claims in documentation.

    No, the engine uses an evidence-first approach that categorizes information as Confirmed, Inferred, or Not Evidenced, ensuring only actual code changes are reported as facts.

    Yes, it can analyze large, multi-file changesets and suggest how to break them down into a logical sequence of atomic, compliant commits for a cleaner branch history.

    The skill is compatible with any AI agent or platform that supports text-based inputs of Git diffs and developer notes, making it versatile for most dev environments.

    You receive the core logic and configuration required to transform raw Git data into structured, audit-ready documentation, including the evidence-based categorization engine.

    The skill requires a text-based Git diff, a file list, or brief developer notes; it does not need direct access to your local repository or the ability to execute code.

    New in Technical Documentation

    Free