개발 스킬

Implement layered configuration in Go with spf13/viper, combining command flags, environment variables, and configuration files under a fixed priority order. Covers mapping values into structs, reloading changed files, and keeping configuration state separate across tests.

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

• Combining configuration files, environment variables, and command flags
• Mapping nested settings into Go structs
• Reloading configuration after file changes

Choose Go libraries and frameworks for web, database, testing, logging, and messaging tasks. Compare candidates with standard library options, checking maintenance, licenses, adoption, and dependency complexity before deciding what to add to a project.

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

• Choose a library for a Go project
• Compare libraries for the same task
• Check whether the standard library is enough

Selects and loads relevant Go skills for coding, review, debugging, and setup tasks. It combines complementary guidance, explains overlapping skill roles, and can configure project agent instructions to load Go skills consistently.

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

• Select related skills for Go implementation work
• Combine debugging and panic-prevention guidance
• Distinguish measurement, optimization, and troubleshooting skills

Assess a supplied task and execution contract, then propose one to four workgroups with clear scopes, dependencies, and verification references. Returns a structured plan for a controller to validate and use.

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

• Planning how to divide a development task
• Identifying work that can proceed in parallel
• Defining verification requirements for each workgroup

Turn a high-level task plan into detailed execution notes, an evidence map, acceptance criteria, and worker handoff instructions. Return the documents and a structured JSON manifest for import by the workflow's scripts.

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

• Detailing a task before assigning it to a worker
• Mapping task requirements to supporting evidence
• Preparing acceptance criteria and verification notes

Clear the conversation context of one or more CCB-managed agents while preserving project state. The skill runs the matching ccb clear command and reports its output, with specific handling for DSH sessions.

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

• Clear an agent's context while preserving project state
• Clear several agents' contexts in one command
• Clear a DSH context while retaining old session logs

Consult a historical reference for describing why an agent role is needed, what blocks it, or when it can be released. It separates evidence supplied by the AI session from lifecycle operations owned by the runner script.

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

• Review the boundary between AI sessions and runner operations
• Describe a needed agent role and the reason for requesting it
• Organize blockers and evidence for readiness or release

Carry out one clearly scoped implementation or investigation task, verify the work where possible, and submit evidence to the assigned reviewer. Reports changed paths, verification results, and blockers while preserving controller authority.

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

• Implementing a change within assigned file paths
• Investigating a narrowly defined issue
• Submitting verification evidence to an assigned reviewer

Submit implemented and verified work to its assigned Reviewer, the agent responsible for checking it. Follow a bounded review and repair process, and report completion only after approval, or return a blocked or rework outcome.

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

• Submitting implemented work for review
• Applying requested repairs and resubmitting
• Requiring review approval before completion

Enable or disable disconnect recovery for the current Codex thread running inside tmux, a terminal session manager. Explicit on and off commands control the setting, and the skill reports the command result or error.

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

• Enable disconnect recovery for the current Codex thread
• Disable disconnect recovery for the current Codex thread
• Check the result or error when changing recovery settings

Turn accumulated code maintenance problems into a prioritized ledger. Findings cite files and lines, include severity and estimated effort, and distinguish quick wins from larger fixes. Repeat audits track resolved, new, and continuing issues against the previous ledger.

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

• Prioritize technical debt within a cleanup budget
• Audit architecture, tests, dependencies, and documentation
• Separate quick wins from larger fixes

Prepare a coding brief for an external agent already chosen by the user. Build instructions around that agent’s installed skills, covering goals, constraints, tests, and reporting requirements, while distinguishing handoff preparation from actual execution.

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

• Preparing a coding brief for a chosen agent
• Composing instructions using installed agent skills
• Defining tests and reporting requirements before handoff

Plan relational database improvements for slow queries, indexes, and large table migrations. Document locks, which can block other database operations, alongside rollback steps and verification checks, using the database engine, version, size, and observed query plans.

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

• Plan a migration for a large table with rollback steps
• Evaluate indexes using observed query plans
• Review database locks caused by deployment changes

View coding activity in a board showing each work unit, execution environment, model, elapsed time, and recorded token usage. Missing information is marked unknown, helping you understand observed activity across multiple coding sessions.

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

• Checking coding activity across multiple sessions
• Seeing the model and environment used for each task
• Reviewing recorded token usage and elapsed time

Organize unlabeled issues and pull requests using an existing label list. Sweep the backlog or target one item by number, review the proposed changes first, and apply them when ready to make work easier to browse by area.

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

• Organizing unlabeled issues and pull requests
• Reviewing classification after adding a label
• Preparing an area-based backlog before a release

Review open pull requests whose latest commit has not been checked, or select one by number. Apply repository review rules, inspect surrounding code, and preview findings before optionally posting inline comments on GitHub.

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

• Review a backlog of unchecked pull requests
• Review one pull request by number
• Check surrounding code and required checks

Investigate software slowness, memory leaks, and rising costs through measurement. Identify expensive processing paths, coordinate small reversible fixes, and compare results against a baseline with an explicit limit on acceptable performance regression.

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

• Investigating slow responses with an unknown cause
• Tracing steadily increasing worker memory usage
• Finding token cost hotspots

Organize an accepted implementation plan into separate work units with owners, acceptance criteria, and verification commands. Coordinate parallel or ordered execution, prevent overlapping file edits, and check the integrated result before reporting completion.

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

• Splitting an approved implementation plan into parallel tasks
• Assigning file ownership to coding agents
• Ordering tasks that depend on earlier changes

Turn an agreed code restructuring into a phased plan. Map affected files and dependencies, order the changes, and define checks and rollback points for each phase, producing a reviewable plan before implementation begins.

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

• Plan the extraction of one module from another
• Break a large code restructuring into releasable phases
• Prepare a dependency or framework upgrade

Prepare a reviewable plan for a risky technical change before implementation. Compare alternatives using repository facts and source evidence, document tradeoffs, and define testable acceptance criteria, verification commands, and an implementation handoff after approval.

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

• Planning a risky refactor before implementation
• Comparing technical options and tradeoffs
• Defining acceptance criteria and verification commands

Prepare and supervise terminal commands with an explicit working directory, environment, timeout, and stopping conditions. Organize confirmation for consequential actions and summarize results from observed output, keeping execution plans separate from evidence that commands actually ran.

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

• Define the scope and conditions for a terminal command
• Supervise a test run and summarize its output
• Confirm an installation or deployment before execution

Extract recurring lessons from skills, prompts, work logs, reviews, and failures into proposed agent rules. Identify overlaps and conflicts with existing guidance, and prepare candidates for human review before any approved implementation.

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

• Turning repeated failures into proposed agent rules
• Checking proposed rules against existing guidance
• Reviewing lessons before updating prompts or skills

Clarify inconsistent project terms using repository evidence and reviewed definitions. Answer straightforward questions, organize unresolved terminology decisions by their dependencies, and prepare a shared understanding before implementation planning or handoff.

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

• Aligning project terms before feature planning
• Checking the meaning and source of a project term
• Resolving conflicting names across code and documentation

Prepare Rust changes by clarifying ownership, borrowing, error types, and public APIs. Produce an implementation plan and verification checklist, with additional checks for undefined behavior when unsafe code or foreign function interfaces are involved.

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

• Planning fixes for borrow checker errors
• Clarifying ownership and lifetime boundaries
• Defining error types and public API changes