How does 'explain my pr' improve the standard code review process?

This skill transforms technical Git diffs into structured, plain-language reports, helping non-technical managers understand the business impact of code changes while providing reviewers with clear ASCII call flows and verification checklists.

Are there specific programming languages or frameworks I need to use?

The skill works with any programming language or framework, as long as the project uses Git for version control and the agent has access to the standard Git CLI.

What exactly is included in the skill purchase?

Upon purchase, you receive the full skill package including the automated documentation template, the ASCII architecture visualization engine, and a set of pre-configured reviewer checklist generators.

Which AI agents or development environments is this skill compatible with?

This skill is designed to run within any AI agent environment that supports filesystem access and Git CLI integration, outputting standardized GitHub-flavored Markdown files.

How difficult is the initial setup for this skill?

Setup is minimal: once the skill is added to your agent, you simply provide a git diff or branch reference, and it automatically handles the analysis and document generation in your specified directory.

Are there any limitations on the size or type of Merge Requests it can handle?

While the skill is highly effective for feature work and refactors, it is currently optimized for single-repository logical units rather than massive multi-repo migrations or monorepo-wide architectural shifts.

Explain My PR (ADHD)

Example session with this skill installed

Explain the changes in my feat/auth-fix branch where I added a retry loop to the token middleware. Explain it for my lead who hasn't seen the code yet.

Read your context and instructions
Compiled the explain my pr

I have analyzed the diff between main and feat/auth-fix. I generated the explanation document at docs/mr-change-explanations/auth-middleware-retry.md.

Why auth-middleware-retry changes when merging feat/auth-fix into main

This MR modifies the token validation logic in the middleware layer. It affects 1 file with 14 additions and 2 deletions.

What is this and why does it matter?

Token Middleware: Intercepts all incoming API requests to validate JWTs.
Resilience: Prevents 401 errors caused by transient network blips to the identity provider.

TL;DR

#	What changed	Why it matters
1	Added exponential backoff	Eliminates request failure on 503 IdP responses.

Big picture

[Client] -> [Middleware] -> [Identity Provider]

                  |                ^

                  +-- (Retry 3x) --+

Fix 1 — Exponential backoff for token validation

What problem this fixes

When the identity provider is under heavy load, it returns a 503. The current code immediately fails with a 401 Unauthorized, forcing users to refresh their browser.

The change in code

main (before)

src/auth/middleware.py:12-15 (main branch):

def validate(token):
    # Directly calls IdP without retry
    return idp_client.verify(token)

feat/auth-fix (after)

src/auth/middleware.py:12-22 (feat/auth-fix branch):

@retry(stop=stop_after_attempt(3), wait=wait_exponential())
def validate(token):
    # Added retry decorator to handle transient IdP errors
    return idp_client.verify(token)

Why this is a safe change

The decorator only catches IdentityServerUnavailable exceptions. All other auth failures (invalid tokens, expired keys) still fail immediately.

Impact table

Consumer	Impact
API Clients	Reduced 401 errors during peak load.
IdP Service	Minor increase in request volume during outages.

Reviewer checklist

Grep wait_exponential to ensure max delay is capped at 2 seconds.
Verify idp_client.verify is idempotent.

Suggested commit message

feat(auth): add exponential backoff to token validation

Implements a 3-attempt retry loop for token verification to handle
transient 503 responses from the identity provider.

Next steps

Review the generated Markdown file in your docs/ folder.
Copy the "Suggested commit message" into your git commit.
Attach this document to your Merge Request description.

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

About this skill

Reviewers often lack the time to parse complex diffs, leading to rubber-stamp approvals or long merge delays. This skill generates manager-friendly documentation that explains the why behind your code changes. It transforms technical git diffs into structured, plain-language reports that highlight impact, safety, and business logic rather than just syntax.

What it does

Drafts MR summaries by analyzing git diffs and logs to produce high-level narrative explanations.
Generates before/after comparisons with branch-specific labels, line ranges, and annotated code snippets.
Visualizes call flows using ASCII architecture diagrams to show how logic changes across the system.
Creates impact tables that explicitly define what remains unchanged for existing consumers versus new opt-in behavior.
Constructs reviewer checklists with specific grep commands and verification steps to speed up the approval process.

How it works

Trigger the skill by providing a git diff or asking to "explain this MR" for a specific branch or feature.
The agent gathers git facts using git diff --stat and git log to identify the scope of changes.
It produces a structured Markdown document saved to docs/mr-change-explanations/ following a standardized management template.

Frameworks & tools

Works with any language or framework accessible via standard Git CLI. Outputs are standard GitHub-flavored Markdown.

Why this beats prompting it yourself

Generic prompts often result in a list of file changes without context. This skill enforces a rigorous structure including safety assessments, ASCII flow diagrams, and side-by-side code citations that map directly to your branch names and line numbers.

Use cases

Explaining complex refactors to non-technical product managers.
Documenting critical bug fixes for compliance or audit trails.
Onboarding new team members to a specific feature's logic.
Standardizing merge request quality across a distributed engineering team.

Known limitations

Requires access to git history and diffs to provide accurate line ranges. Best suited for single logical units or cohesive features rather than massive multi-repo migrations.

How to use

Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

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

Fresh listing

Recently published to Agensi

Free forever

No account required to browse

Explain My PR (ADHD)