Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    PR Change & Risk Writer

    1

    Turn a branch diff into a factual PR brief: changes, risks, test needs, unknowns, and rollback signals.

    Free

    1 installSecurity scanned
    PR Change & Risk Writer

    PR Change & Risk Writer

    Example session with this skill installed

    Write a reviewer-ready PR brief from this diff summary:

    • src/api/users.ts: GET /users/:id now returns 404 instead of { user: null }
    • src/client/user.ts: client now throws UserNotFoundError on 404
    • tests/user-api.test.ts: new 404 test added
    • no UI tests changed

    Do not invent intent or claim tests passed unless the evidence supports it.

    • Read your context and instructions
    • Compiled the pr change
    • Generated the document

    PR CHANGE & RISK BRIEF

    Summary

    This change makes "user not found" explicit at the API boundary. The API now returns HTTP 404, and the client converts that response into UserNotFoundError.

    What changed

    • Changed the not-found API contract from a successful response containing user: null to HTTP 404.
    • Updated the client wrapper to translate 404 into a typed error.
    • Added API-level coverage for the new 404 behavior.

    Why / intent

    Supported: The code consistently moves not-found behavior to an explicit error path.
    Inferred: The likely intent is to make absence easier to distinguish from successful empty data.
    Unknown: Whether all callers are prepared for the new exception behavior.

    Affected behavior

    • API consumers expecting 200 + user: null.
    • Client callers that previously handled a nullable user.
    • UI flows that may not catch UserNotFoundError.

    Risk map

    RiskEvidenceWhat to verify
    Unhandled client exceptionClient now throws on 404Check all call sites for error handling
    External API compatibilityResponse contract changedConfirm external consumers or versioning
    UI regressionNo UI tests changedExercise not-found user flows

    Test status

    Visible in diff: API 404 case.
    Still needed: Client caller/UI behavior for UserNotFoundError.
    Not verified: External consumer compatibility.

    Reviewer focus

    1. Search all client call sites for assumptions that user may be null.
    2. Verify whether the API is public or versioned.
    3. Confirm UI behavior for missing users.

    Merge / rollback signals

    Block merge if: Existing callers cannot handle UserNotFoundError.
    Rollback / stop if: Not-found traffic begins producing uncaught client errors.

    Suggested PR description

    Changes user-not-found handling from 200 + null to an explicit 404 response and maps that response to UserNotFoundError in the client. Adds API-level coverage for the 404 case.

    Before merge, verify downstream callers and UI flows that previously handled a nullable user.

    What would change this assessment

    • Evidence that the API is internal and all callers were updated elsewhere.
    • Existing UI coverage for the new typed error path.

    pr-change-risk-writer.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Turn a code diff into a PR a reviewer can actually trust.

    Most AI PR writers are good at making changes sound complete. That is also the problem: a diff can show what changed without proving why it changed, whether it is safe, whether tests passed, or whether downstream callers are ready.

    PR Change & Risk Writer produces a factual review brief from the code that actually changed.

    What it does

    • Identifies the real center of the change instead of narrating every file equally.

    • Separates observed code changes from inferred intent and unknown context.

    • Maps changed behavior, public interfaces, data paths, configuration, dependencies, and operational surfaces.

    • Highlights concrete risks only where the diff supports them.

    • Shows reviewers where attention has the highest value.

    • Separates tests visible in the diff from tests that are still needed or not verified.

    • Flags claims such as “no breaking changes,” “fully tested,” or “safe migration” when the evidence does not support them.

    • Defines merge blockers and rollback or stop signals when the change warrants them.

    • Produces a clean, copy-ready PR description at the end.

    Use it when

    • a branch has grown too large to summarize manually
    • a PR description needs to be factual instead of promotional
    • reviewers need to know where the real risk is
    • an API, schema, auth, dependency, migration, retry, or state path changed
    • you need to distinguish actual test evidence from assumed coverage
    • a generated PR description sounds polished but may be overstating what the diff proves

    What you get

    1. Factual summary
    2. What changed
    3. Supported vs inferred intent
    4. Affected behavior
    5. Risk map
    6. Test status
    7. Reviewer focus
    8. Merge / rollback signals
    9. Copy-ready PR description
    10. What would change the assessment

    Why it is different

    A diff is evidence of change, not proof of intent or safety. This skill keeps those layers separate so reviewers spend less time checking claims the PR description should never have made.

    Known limitations

    The skill cannot prove production safety, backward compatibility, test success, or business intent from a diff alone. It explicitly marks those gaps when the supporting evidence is missing.

    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 11 days ago

    • Free to download with an account

    Listed11 days ago

    What's inside

    Frequently Asked Questions