Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Commit & PR Writer: Atomic Commits + Reviewer-Ready PRs

    2

    "fix stuff", "wip", one giant commit with five unrelated changes, an empty PR description...

    Free

    10 uses5.0 (1 review)
    Commit & PR Writer: Atomic Commits + Reviewer-Ready PRs

    Commit & PR Writer: Atomic Commits + Reviewer-Ready PRs

    Example session with this skill installed

    I have a bunch of changes. Split them into proper commits and write the PR description.

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

    Example output on a sample TypeScript monorepo.

    Summary

    Found 11 changed files. Recent history uses Conventional Commits with scopes and Jira refs (CHK-123). The changes contain 3 independent intents, so I propose 3 atomic commits. apps/api/.env.local was modified but

    not staged (contains secrets).

    Proposed commits

    1. refactor(api): extract pricing service from checkout controller
    
       Pricing logic was duplicated in checkout and quotes. Moving it to
       PricingService makes the retry fix below testable in isolation.
    
    2. feat(checkout): support retrying failed payments
    
       Customers lost their cart when a payment failed. Retries now reuse
       the pending order and apply the discount only once.
    
       - add discount_applied column (backwards compatible migration)
       - new POST /checkout/:id/retry endpoint
    
       Refs: CHK-482
    
    3. chore(deps): bump zod to 3.23.8
    

    PR description

    Title: feat(checkout): support retrying failed payments

    
    ## Summary
    Failed payments can now be retried without losing the cart or re-applying discounts (CHK-482).
    
    ## Changes
    - New `POST /checkout/:id/retry` endpoint
    - Pricing logic extracted to `PricingService` (no behaviour change)
    - `discount_applied` column on orders
    
    ## How to test
    1. `pnpm db:migrate && pnpm test checkout`
    2. Pay with test card 4000 0000 0000 0341 (declined), then retry with 4242 4242 4242 4242
    3. Verify the discount is applied once and the cart is intact
    
    ## Risks & rollout
    - Migration adds a nullable column: safe for zero-downtime deploys
    - Retry endpoint behind `checkout_retry` feature flag
    
    ## Checklist
    - [x] Tests added/updated
    - [x] Docs updated
    - [ ] Screenshots (no UI changes)
    

    Next step: reply "commit" to create the 3 commits, or "commit and open PR" to also create a draft PR with gh.

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

    About this skill

    "fix stuff", "wip", one giant commit with five unrelated changes, an empty PR description... Messy history slows down reviews, makes git blame useless and breaks automated changelogs.

    This skill reads your changes, groups them by intent and writes the commits and PR description a senior engineer would.

    What it does

    • Learns your repo's style: Conventional Commits, gitmoji, ticket prefixes (ABC-123), language and casing, detected from recent history. Uses your .github/pull_request_template.md if present.
    • Splits into atomic commits: groups hunks by intent, not by file (feature + its tests together; refactors, formatting and dependency bumps separately) and stages them with git add -p.
    • Writes great messages: imperative summary of 72 characters or less, a body explaining why, issue refs and BREAKING CHANGE notes with migration hints when needed.
    • Writes the PR description: summary, changes, exact testing steps, risks and rollout (migrations, flags, compatibility) and a checklist.
    • Creates the PR (optional): gh pr create as a draft when you ask.
    • Guards your repo: warns about .env files, secrets, build output and large binaries instead of committing them. Never pushes unless asked.

    Workflow

    1. Shows the proposed commit plan and messages.
    2. Commits after your OK (or directly if you say "just commit").
    3. Generates the PR title and body from all commits on the branch.

    Best for

    • Teams using Conventional Commits, semantic-release or changelog tools
    • Cleaning up a big working tree before review
    • Developers who hate writing PR descriptions

    • Very large diffs with mixed changes inside the same hunk may need a manual git add -p decision; it will ask instead of guessing.
    • Automatic PR creation supports GitHub via gh; for GitLab/Bitbucket it outputs the title and body for you to paste.
    • It explains why a change was made from code and context; for business reasons not visible in the code it may ask you for one line.

    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

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    This skill has been used 10 times.

    Trust & safety

    Security scan

    Security scan passed 11 days ago

    • Free with an Agensi account

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files

    Read Files: reads the diff, recent commit history and your PR template. Terminal: runs git (status, diff, add -p, commit) and optionally gh to open a draft PR. It never pushes or opens a PR unless you ask, and it refuses to commit secrets or .env files.

    Listed11 days ago
    Updated5 days ago

    What's inside

    Frequently Asked Questions

    No. It detects your repository's existing style (Conventional Commits, gitmoji, ticket prefixes, language) and follows it. Conventional Commits is only the default for new repos.

    No. It shows the commit plan and messages first and commits after your confirmation, unless you explicitly say "just commit". It never pushes unless asked.

    Yes. It groups hunks by intent and stages them separately with git add -p, so features, refactors, formatting and dependency bumps end up in their own commits.

    Yes. If .github/pull_request_template.md exists it fills it in; otherwise it uses a proven structure: summary, changes, how to test, risks and checklist.

    It warns about .env files, credentials, build output and large binaries and leaves them unstaged.

    Commits work with any Git host. Automatic PR creation uses the GitHub CLI; for other hosts it gives you the title and description ready to paste.

    New in Code Quality & Review