Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Research the following topic thoroughly: $ARGUMENTS
Identify the scope of the research. Parse the topic into concrete searchable terms: class names, function names, file name patterns, configuration keys, or framework-specific terms.
Search broadly before reading deeply:
*auth*, *middleware*, *.config.*)Read the most relevant files completely. Do not skim. Missing a detail in a critical file leads to incorrect conclusions.
For key files, check recent git history to understand why things are the way they are:
git log --oneline --follow -20 <filepath>
Read the most informative commit messages. If a commit message references a PR or issue number, note it.
Follow import and dependency chains one level deep. If the main file imports from three other modules, read those modules too.
Synthesize findings into a structured report with these sections:
Overview What this system or component does, in two to four sentences. Write for someone who has never touched this codebase.
Key files A table: file path | one-line description of its role. Include every file you read that was materially relevant.
How it works The main flow, data structures, and key design decisions. Use concrete terms: function names, type names, config keys. Reference file paths and approximate line numbers for the most important details.
Recent changes What changed in the last 20 commits in the relevant area, and why (based on commit messages and diff context).
Open questions Anything that is unclear from the code alone and would benefit from asking a team member or reading documentation. Be specific.
Be precise. If you are uncertain, say so. Do not infer things that are not in the code.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.