Explain recent changes and provide a structured summary with security checks
| name | explain-changes |
| description | Explain recent changes and provide a structured summary with security checks |
Review the recent changes and provide:
Summary: What was built or changed? Explain in 2-3 sentences.
Files changed: List the files that were added or modified, grouped by area (e.g., API routes, components, database, utils).
Security check:
Risk areas: Which files or functions are most likely to cause problems? Why?
Edge cases: What scenarios might break this? What hasn't been tested?
Missing pieces: Based on what this feature is supposed to do, is anything obviously incomplete or not wired up?
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.
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
Cursor Cloud VM setup and service startup instructions for local development
Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.
Commit changes and open a pull request with safe metadata
Review prompt and tool-description changes in a branch or PR. Use when asked to audit system prompts, prompt builders, tool descriptions, prompt inputs, or nearby evals/tests; summarize what changed; identify guidance that feels eval-shaped or too heavy for product use; and find repeated instructions between the main prompt and tool descriptions.
Add a new changelog entry to docs/changelog-entries/
