branch change audit

    1

    Audit branch changes against main, grouping modified files by service and status for fast PR reviews.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    branch change audit

    Example session with this skill installed

    Run a branch audit against origin/main for the services/ directory and group the changes.

    • Read your context and instructions
    • Compiled the branch change audit

    I have performed a diff between origin/main and the current branch, focusing on the services/ directory.

    Branch Change Audit

    MetricValue
    Baselineorigin/main
    Total Services2
    Total Files5

    services/api-gateway

    • A services/api-gateway/src/middleware/auth.ts
    • M services/api-gateway/package.json
    • R services/api-gateway/config.yaml <- services/api-gateway/settings.yaml

    services/user-auth

    • M services/user-auth/src/handler.go
    • D services/user-auth/temp_script.sh

    Next steps

    1. Review the renamed config.yaml to ensure no environment variables were lost.
    2. Verify that the deletion of temp_script.sh does not break any local CI scripts.
    3. Run scripts/generate_audit.sh to save this report as CHANGE_AUDIT.md for the PR.

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

    About this skill

    Manual branch reviews are prone to missing files, especially in monorepos where changes span multiple services. Identifying exactly what changed since branching from main requires tedious git commands and manual grouping.

    What it does

    • Service-level grouping Categorizes changes by service or directory key using path segment analysis.
    • Status preservation Tracks and reports the specific nature of changes including additions, modifications, deletions, and renames.
    • Automated baseline detection Resolves the correct upstream branch automatically, checking symbolic refs and remote HEAD.
    • Rename tracking Clearly maps file movements showing the transition from old paths to new locations.
    • Scope filtering Limits audits to specific sub-directories like apps/ or services/ when requested.

    How it works

    1. Identify baseline The skill probes the environment to find the upstream target branch, typically origin/main or origin/master.
    2. Execute diff Runs a name-status diff between the baseline and the current HEAD to capture the exact delta.
    3. Parse and group Organizes raw git output into a structured hierarchy based on repository folders.
    4. Generate report Outputs a summary to the chat or writes a CHANGE_AUDIT.md file for PR documentation.

    Frameworks & tools

    This skill utilizes Git CLI and shell scripting. It is compatible with any repository structure, including complex monorepos managed with tools like Nx, Turborepo, or Lerna.

    Why this beats prompting it yourself

    Standard LLM prompts often hallucinate change lists or fail to correctly resolve the git baseline. This skill uses specific CLI sequences to ensure every file status is accurate and properly grouped by service, saving you from manual diff parsing.

    Use cases

    • Generating a pre-PR impact assessment to verify only intended files were touched.
    • Auditing monorepo changes to identify which microservices require deployment.
    • Creating a structured changelog for team review sessions.
    • Troubleshooting unexpected behavior by listing all modifications since the last stable merge.

    Known limitations

    Requires a local git environment with an established origin to detect the baseline automatically. Does not include unstaged or uncommitted local changes in the branch-to-branch diff.

    Requires Git CLI access. Only audits committed changes (HEAD vs baseline); does not include unstaged work. Works best with repositories using standard directory-based service structures.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill automates the tedious process of manual diffing by using specific Git CLI commands to identify exactly what changed between your branch and the main baseline, then groups those changes by service/directory for easy reading.

    Yes, it is specifically designed for complex structures and is compatible with tools like Nx, Lerna, and Turborepo, allowing you to filter audits to specific folders like /apps or /services.

    The skill requires a local git environment with an established 'origin' remote; it uses this to automatically detect your upstream branch and resolve the correct baseline for the audit.

    The skill focuses on committed code; it audits the delta between your current HEAD and the upstream branch, meaning unstaged or uncommitted local changes are not included in the report.

    You receive the fully functional skill ready to be imported into your AI agent's environment, enabling you to generate instant change summaries or structured CHANGE_AUDIT.md files.

    Unlike generic prompts that might hallucinate file names or miss renames, this skill uses precise path segment analysis and rename tracking to ensure 100% accuracy in the change report.

    New in Technical Documentation