Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+20 more

    git pr builder

    1

    Generate Conventional Commits, structured PR descriptions, and changelogs directly from your git diffs.

    Free

    2 installsSecurity scanned
    git pr builder

    git pr builder

    Example session with this skill installed

    I just refactored the auth middleware in src/middleware/auth.ts to use JWT instead of sessions and fixed a bug in login.ts. Write a commit message and PR description.

    • Read your context and instructions
    • Compiled the git pr builder

    I have analyzed the changes in your authentication logic. I have split the concerns into a primary refactor and a bug fix.

    Commit message

    refactor(auth): migrate middleware from session-based to JWT
fix(auth): resolve null pointer exception in login handler

    PR description

    Summary

    This change replaces the legacy session-based authentication middleware with a stateless JWT implementation. This improves scalability and allows for easier horizontal scaling of the API tier. It also addresses a crash in the login flow when an invalid email format was provided.

    Changes

    src/middleware/auth.ts: Replaced session-store dependency with jsonwebtoken. Implemented verifyToken strategy.

    src/handlers/login.ts: Added validation check for user object before accessing properties to prevent runtime errors.

    • package.json: Added jsonwebtoken and removed express-session.

    How to test

    1. Run npm install to update dependencies.
    2. Start the server and attempt to access a protected route without a header; verify 401.
    3. Call /login with valid credentials and verify a JWT is returned.
    4. Provide the JWT in the Authorization: Bearer <token> header and verify access.

    Screenshots / before-after

    [Not applicable for middleware changes]

    Rollback plan

    git revert <commit-hash> and reinstall express-session if the JWT signature verification fails in production.

    Related

    Closes # [Insert Issue Number]

    Next steps

    • Review the generated PR description and fill in the issue number.
    • Verify that your .env file contains the JWT_SECRET required for the new middleware.
    package.json

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

    About this skill

    Writing git history and pull request descriptions manually is a productivity drain that leads to inconsistent repos and frustrated reviewers. This skill automates the generation of Conventional Commits, detailed PR templates, and user-facing changelogs by analyzing your git diffs and local context. It eliminates the friction of documentation so you can focus on shipping code.

    What it does

    • Conventional Commits generates structured, imperative-style commit messages following industry standards.
    • Diff analysis groups related file changes into logical blocks for cleaner reviewer navigation.
    • PR templates builds full descriptions including testing steps, rollback plans, and issue links.
    • Changelog generation translates technical diffs into user-centric release notes categorized by impact.
    • Context matching reads your existing git log to match the specific tone and conventions of your team.

    How it works

    1. Run a command like git diff or provide a branch name for the skill to analyze.
    2. Specify the scope of output needed, such as a commit message, a PR description, or a changelog entry.
    3. Review the generated documentation, which fills in technical details while highlighting gaps for manual input.
    4. Apply the output directly to your version control workflow.

    Frameworks & tools

    This skill works with any project using Git for version control. It follows the Conventional Commits specification and is compatible with GitHub, GitLab, and Bitbucket workflows.

    Why this beats prompting it yourself

    Generic prompts often hallucinate file changes or fail to follow strict character limits for commit headers. This skill is hardcoded to respect the 72-character rule, group diff concerns logically, and prioritize the "why" over the "what" in PR descriptions.

    Use cases

    • Generating a professional PR description for a complex feature branch.
    • Creating semantic commit messages that match a team's existing repository style.
    • Compiling user-facing release notes from a series of technical bug fixes.
    • Drafting a safe rollback plan for a high-risk refactor.

    Known limitations

    Does not perform destructive git actions like rebasing or pushing. Requires access to the local git repository or a provided diff to function accurately.

    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 any payment.

    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 installs

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed today

    • Free with an Agensi account

    Requires

    Git

    Listed20 days ago

    What's inside

    Frequently Asked Questions