mcpField
E
explain-changes

explain-changes

github.com/elie222Testing & quality12.8k38 installsUpdated today
Repository

About explain-changes

A review skill that structures change reviews around implementation, security, risks, edge cases, and missing work. It is intended for developers assessing recent code changes and identifying questions to verify.

Key features

  1. 01Summarize implementation changes
  2. 02Group added or modified files by area
  3. 03Check authentication, validation, and secret handling
  4. 04Identify risk areas and edge cases
  5. 05Flag incomplete work and open questions

Use cases

  1. 01Reviewing a feature before merging
  2. 02Checking security implications of recent edits
  3. 03Finding untested scenarios and incomplete wiring

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/elie222/inbox-zero --skill explain-changes

After installing, type/explain-changesin Claude Code to confirm it loaded.

Details

From the project README

Review the recent changes and provide:

  1. Summary: What was built or changed? Explain in 2-3 sentences.

  2. Files changed: List the files that were added or modified, grouped by area (e.g., API routes, components, database, utils).

  3. Security check:

    • Any new API endpoints? Are they properly authenticated?
    • Any database writes? Is the input validated?
    • Any external API calls? Are secrets handled correctly?
    • Any user-facing inputs? Are they sanitized?

  4. Risk areas: Which files or functions are most likely to cause problems? Why?

  5. Edge cases: What scenarios might break this? What hasn't been tested?

  6. Missing pieces: Based on what this feature is supposed to do, is anything obviously incomplete or not wired up?

  7. Questions for me: Anything you're uncertain about or made assumptions on that I should verify?

Be concise. Flag problems, don't over-explain things that are fine.

Comments

Markdown supported