Investigate two separate areas of the codebase simultaneously and combine findings into a comparison report. Use when you need research on two independent topics at once, want to compare two subsystems, or need to understand how two components relate to each other.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Investigate these two topics in parallel using separate Explore subagents:
Spawn two Explore subagents simultaneously — one per topic. Give each a self-contained research prompt that includes:
Do not run the subagents sequentially. Start both at the same time.
Wait for both subagents to return their results.
Combine the findings into a single comparison report with these sections:
Topic 1 findings — summary of what the first subagent found
Topic 2 findings — summary of what the second subagent found
Similarities — patterns, libraries, approaches, or design decisions shared between the two topics
Differences — how they diverge: in scale, in architecture, in data model, in error handling, or in how they are tested
Recommendation — if the user is trying to make a decision (e.g., which approach to follow, which subsystem to extend), give a direct recommendation with reasoning. If the topics are purely informational (e.g., understanding two independent systems), omit this section.
This skill does not use context: fork — it runs inline in your main conversation. This is intentional: a forked skill cannot spawn additional subagents, so any skill that needs to orchestrate multiple workers must run in the main context and delegate the worker tasks from there. The main conversation is the orchestrator; the Explore subagents are the workers.
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.