Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a git branch named after a GitHub issue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.