Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    git commit pr writer

    1

    Standardize your Git history with diff-based Conventional Commits and structured PR descriptions.

    Free

    1 installSecurity scanned

    git commit pr writer

    Example session with this skill installed

    Generate a commit message and PR description for my staged changes. I've updated the auth middleware to handle JWT expiration and added a unit test in auth_test.go.

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

    I have analyzed the staged changes in middleware/auth.go and middleware/auth_test.go. The diff shows a new logic block for token.Expired errors and a corresponding test case.

    Git Metadata & PR Description

    Commit Message:

    fix(auth): handle JWT expiration in middleware

    Pull Request Description:

    Summary

    This change updates the authentication middleware to explicitly catch and handle expired JSON Web Tokens. Previously, expired tokens could trigger a generic 500 error; they now return a specific unauthorized response.

    What changed

    • Added check for ErrExpiredToken in the Authorize middleware.
    • Updated the response header to include WWW-Authenticate: Bearer error="invalid_token".
    • Added a new test case in auth_test.go to verify expiration handling.

    Why

    Improving error clarity for frontend clients to trigger automatic re-authentication flows when a session expires.

    Impact & Risk

    • User Impact: Better UX; clients can now distinguish between "bad token" and "expired token".
    • Technical Impact: Minimal. Only affects the auth middleware layer.
    • Risk: Low. The change is isolated to error handling logic.

    Testing

    • Status: Verified (Based on new test coverage provided in diff).
    • Details: TestAuthMiddleware_ExpiredToken passes locally.

    Next steps

    1. Run git commit -m "fix(auth): handle JWT expiration in middleware"
    2. Verify if a corresponding ticket in Jira/GitHub needs to be linked.
    3. Push the branch and paste the PR description above into the repository UI.

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

    About this skill

    The problem

    Writing meaningful commit messages and PR descriptions is a repetitive tax on developer time. Manual summaries often miss subtle side effects, lack consistent formatting, or include "magic" claims about testing and intent that the code doesn't actually support.

    What it does

    • Analyzes staged diffs and branch comparisons to extract objective behavior changes.
    • Maps code modifications to strictly accurate Conventional Commit types like feat, fix, or refactor.
    • Identifies genuine breaking changes based on API removals and schema migrations rather than just diff size.
    • Generates structured PR descriptions including technical impact, risk assessment, and reviewer focus areas.
    • Flags unrelated changes in a single diff and suggests splitting them into distinct commits.

    Why this beats prompting it yourself

    Generic LLM prompts tend to hallucinate test results or invent issue numbers to fill templates. This skill enforces a "diff-as-evidence" policy, ensuring every claim in your PR is backed by actual code changes while strictly adhering to Conventional Commit standards without the fluff.

    Use cases

    • Generating standardized commit messages for teams enforcing Conventional Commits.
    • Drafting comprehensive PR descriptions for complex refactors or multi-file features.
    • Creating release notes by synthesizing a range of commits into a change summary.
    • Auditing staged changes to ensure no sensitive data or secrets are being committed.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    1 install

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 17 days ago

    • Free to download with an account

    Listed17 days ago

    What's inside

    Frequently Asked Questions