개발 스킬

Manage GitHub issues and pull requests, proposed code changes, using the gh command-line tool. Create and inspect discussions, check automated test results, investigate failed logs, rerun jobs, and track authorized merges through to their verified status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating and updating issues or pull requests
• Checking pull request reviews and automated checks
• Investigating failed CI logs and rerunning jobs

Bundle a question and selected project files for a second AI model to review code, investigate bugs, or assess design options. Preview the files and token usage before running through an API or browser.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting a second AI opinion on code
• Investigating errors with relevant project files
• Comparing design and refactoring options

Create or revise agent skills by defining when they run, what they produce, and how their files are organized. Validate SKILL.md settings, resource links, and changed helper scripts before completing the work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a skill for a recurring workflow
• Repairing an existing SKILL.md
• Organizing bundled references and scripts

Investigate performance bottlenecks in REA analysis workflows and improve caching, queries, or shared processing. Compare completed tasks before and after changes while preserving correct results, examined coverage, and access to supporting evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow analysis workflows
• Reviewing cache keys and invalidation
• Reducing CPU and memory use

Investigate shipped applications, binaries, packages, and firmware with REA to explain features, compare versions, or guide reconstruction. Use decompiled code and runtime observations where needed, keeping observed facts, inferred behavior, and unresolved questions clearly separated.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explaining features in a shipped application
• Comparing behavior across application versions
• Inspecting binaries and packaged resources

Design or change REA investigation tools by defining responsibilities, inputs, results, and CLI or MCP interfaces. Produce a proposal that explains how Evidence records should be interpreted, compares the nearest existing alternative, and outlines verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a new REA investigation tool
• Reviewing CLI or MCP inputs and results
• Defining provider responsibilities and Evidence meaning

Carry out an implementation plan by assigning each task to a separate agent, then reviewing specification compliance and code quality. Keep progress in files and review the complete set of changes after all tasks are finished.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a plan with mostly independent tasks
• Reviewing specification compliance after each task
• Resuming work from recorded progress

Investigate bugs, failing tests, and unexpected behavior using reproduction steps, logs, and recent changes. Follow a structured process to identify the root cause, test a specific explanation, and verify the resulting fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating failing tests
• Tracing the cause of a production bug
• Finding where a build or integration breaks

Create, revise, and validate agent skills through tests that compare behavior with and without the instructions. It helps identify unclear guidance, choose an appropriate document structure, and refine wording before deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a reusable agent skill
• Revising instructions agents misinterpret
• Testing a skill before deployment

Turn specifications or requirements into an implementation plan before coding begins. Break work into testable tasks with exact files, function definitions, test assertions, and verification commands, so another developer or agent can follow the plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a feature before writing code
• Breaking requirements into testable tasks
• Handing implementation work to another developer or agent

Carry out an existing implementation plan in one session, task by task. Verify each step with tests, record progress and decisions in a file, and finish with a review of all changes on the branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a prepared development plan
• Executing tasks without implementer subagents
• Resuming work from a progress record

Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting feature work in a separate workspace
• Preparing a workspace before executing an implementation plan
• Checking whether a workspace is already isolated

Requests a code review from a separate agent after implementation or before merging. It provides the change summary, requirements, and commit range, then guides follow-up work according to the severity of the findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a major feature after implementation
• Checking changes before merging
• Getting another perspective on a complex bug fix

Examine superpowers session records to document repeated work, departures from plans, delays, and token usage. Produce an evidence-based report with file and line references, and prepare bug-report material when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating repeated work or departures from a plan
• Checking session duration and token usage
• Tracing whether a skill was invoked

Finish completed development work by checking the full test suite and presenting integration choices: merge locally, create a Pull Request, or keep the branch. It carries out the selected path and handles workspace cleanup accordingly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Merging a completed feature locally
• Pushing a branch and creating a Pull Request
• Keeping completed work for later integration

Assign independent bugs or test failures to separate agents that work at the same time. Define each agent’s scope and expected report, then check for conflicting changes and run the full test suite before integrating fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating test failures with unrelated causes
• Fixing independent problems in separate subsystems
• Defining focused tasks for multiple agents

Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying ambiguous code review comments
• Checking whether suggested changes preserve compatibility
• Assessing whether a requested feature is actually used

Review a coding session and identify improvements to the agent’s working environment. Examine file navigation, automated checks, instructions, tool use, and information access, then present proposed changes in order of severity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a coding session that took too long
• Finding automated checks for recurring mistakes
• Simplifying agent instructions

Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating an error that is hard to reproduce
• Finding the cause of a performance slowdown
• Testing an intermittent failure repeatedly

Sharpen a plan or design through persistent questioning while creating documentation along the way. The resulting documents include architecture decision records, which capture design choices, and a glossary of terms used in the discussion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sharpening a plan through detailed questions
• Examining a design through an interview
• Documenting design decisions during discussion

Set up automated checks before each Git commit using Husky and lint-staged. Format staged files with Prettier, run existing type checks and tests, and verify the setup using the repository's package manager.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding automated checks before commits
• Formatting staged files with Prettier
• Running existing type checks and tests before commits

Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing changes on a branch or pull request
• Checking changes since a chosen commit or tag
• Checking compliance with documented coding standards

Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Simplifying a module's interface
• Bringing scattered complexity into one module
• Choosing where implementations can be swapped

Review a codebase for structural problems that make understanding and testing difficult. Compare refactoring candidates in an HTML report with before-and-after diagrams, then explore the chosen option through questions about constraints, design, and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review architecture in frequently changed code
• Compare refactoring options with before-and-after diagrams
• Explore module designs that are easier to test