개발 스킬

Help Claude Code carry long coding tasks across session resets. The skill filters command output, records significant actions and pending tasks in `session.log`, and uses that log to announce what remains and continue work when a new session starts.

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

• Keeping a long Claude Code task organized
• Reducing verbose command output in context
• Resuming pending work after a session reset

Create a clear CONTRIBUTING.md for an open-source project, covering local setup, ways to contribute, the change and pull request workflow, project standards, review expectations, and where to ask for help.

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

• Draft a CONTRIBUTING.md
• Explain setup for new contributors
• Set expectations for pull requests

Simplify working code by removing unused abstractions, needless indirection, and confusing control flow while preserving behavior. The result includes verification evidence and a ledger explaining each removal and the future flexibility it gives up.

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

• Simplifying a newly completed feature
• Reducing over-engineering in AI-generated code
• Making a hard-to-follow file easier to read

Make unfamiliar code easier to understand with a one-line summary and a step-by-step walkthrough tailored to the reader. It also points out non-obvious behavior, assumptions, edge cases, and bugs or code smells noticed while reading.

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

• Understanding an unfamiliar code snippet
• Walking through a function's logic
• Getting oriented in a code file

Creates a focused pull request review checklist tailored to the programming language, change type, and risk level. It covers relevant correctness and testing checks, common pitfalls, review depth, and concrete conditions for approval or requesting changes.

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

• Prepare checks for a bug fix pull request
• Review a high-risk dependency upgrade
• Tailor a checklist to a language and framework

Reviews a pull request or code diff for correctness, security, design, tests, and readability. Findings are ranked from blocking issues to optional nits, with reasons and concrete suggestions, alongside specific strengths and a clear approve, request-changes, or comment verdict.

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

• Reviewing a pull request before merge
• Giving prioritized feedback on a code change
• Checking a diff for security or design concerns

Helps prepare a project context file such as CLAUDE.md for an AI coding agent. It captures the project structure, conventions, exact build and test commands, and safety guardrails so the agent can navigate the codebase and verify its work.

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

• Preparing a CLAUDE.md for a code repository
• Helping Claude Code follow project conventions
• Explaining a codebase to an AI coding agent

Guide Claude through a four-stage coding workflow: confirm a written plan, isolate changes on a feature branch, write tests before implementation, and review the result for correctness and code quality before presenting it.

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

• Plan a complex coding task before implementation
• Keep changes on a separate feature branch
• Write and run tests before coding

Turn a vague software problem into a reproducible bug report. It organizes a clear title, exact steps, expected and actual results, environment details, severity and priority, and evidence, while marking assumptions and keeping suspected causes separate from observed facts.

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

• Turning “it’s broken” into a usable ticket
• Documenting a bug with clear reproduction steps
• Separating observed behavior from a suspected cause

Turn an unclear bug report into an actionable triage record with reproducible steps, environment details, justified severity and priority, a likely component and owner queue, and a duplicate check. It flags missing information instead of filling gaps with guesses.

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

• Prepare a bug report for the backlog
• Assess severity and fix priority
• Clarify reproduction steps and environment

Turn a real commit range into release notes people can understand. The skill groups changes by user impact, combines commits for the same feature, explains breaking changes and upgrade steps, and produces a changelog ready to paste into a release.

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

• Draft release notes from commits
• Summarize changes since the last tag
• Explain changes between two refs to users

Investigate software bugs through reliable reproduction, narrowing the faulty area, and testing ranked cause hypotheses. Get a structured diagnosis with evidence for the root cause, a fix, and a regression test to help prevent the defect from returning.

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

• Debugging a defect with unclear cause
• Investigating an intermittent test failure
• Narrowing down where a bug occurs

Turn raw git commits, a commit list, or developer release notes into a user-facing changelog entry. Organize changes under a version header and relevant categories, call out breaking changes with migration guidance, and omit sections that have no entries.

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

• Writing release notes from a git log
• Creating a CHANGELOG.md entry for a version
• Explaining changes to product users

Create a versioning strategy for an API or service, tailored to its API type, consumers, and constraints. The document sets a version scheme and lifecycle, classifies breaking changes, and includes a deprecation timeline, migration guide structure, and client communication templates.

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

• Defining a versioning policy for an API
• Planning a version deprecation and sunset
• Deciding whether a change breaks existing clients

Document a technical or architectural choice in a structured ADR, a record of why a decision was made. Capture its context, options, chosen approach, consequences, tradeoffs, risks, and conditions that could prompt a review.

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

• Recording why a technical approach was selected
• Comparing options and documenting why alternatives were rejected
• Writing an ADR for a system or technology decision

Turn a system description into a renderable Mermaid architecture diagram. Group services, clients, data stores, and external dependencies into logical layers, show connection direction and sync or async flows, then add a component legend and notes.

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

• Map services and data flows
• Explain how system components connect
• Show dependencies and data stores

Review AI-written or AI-assisted code for subtle logic errors, invented or misused APIs, weak tests, duplicate utilities, unnecessary complexity, leftover scaffolding, and security shortcuts. Get severity-ranked findings, practical verification steps, and a checklist tailored to the codebase.

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

• Reviewing an AI-generated pull request
• Checking whether tests catch likely breakages
• Verifying external APIs used by a code change

Prepare an existing codebase for an evo optimization run. Explore its goals and evaluations, suggest promising optimization targets when needed, set up a benchmark and instrumentation in a baseline worktree, and launch the first experiment so results can be compared against a recorded baseline.

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

• Start an evo optimization run for a repository
• Find useful optimization targets in a codebase
• Set up a benchmark and baseline experiment

Turn the best valid result from an evo run into a focused change that maintainers can review. Rebuild the minimal diff, check that tests and project conventions remain intact, verify the result, and prepare a mergeability report; use a pull request for repositories with a remote or merge locally otherwise.

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

• Prepare the best evo result for review
• Distill an experiment into a minimal code change
• Create a pull request for a winning experiment

Resolve an Octane or Octane library defect at the repository that owns it. When the fix is clear, add regression coverage and prepare a pull request; otherwise, file an actionable issue with reproduction evidence and affected versions.

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

• Fixing a confirmed Octane defect in its owning repository
• Preparing a reproducible issue when the fix is unclear
• Reporting an affected package and version with expected and actual behavior

Use TanStack DB from Octane components to display live query results, handle loading and errors, paginate data, and pace mutations such as frequent text edits. The skill also covers query dependencies and live effects.

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

• Display filtered, live-updating collection data in an Octane component
• Load query results with Suspense and an Error Boundary
• Add cursor-based pagination to a list

Use this skill to classify an unfamiliar Octane issue, failure, test result, or proposed task. It identifies the likely owning area, issue type, severity, and confidence, then suggests evidence-based next steps and a focused validation command.

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

• Classifying an unfamiliar test failure
• Finding the owner of a reported bug
• Sorting a proposed task before implementation

Route React library work in Octane to the appropriate workflow: use update-bindings for maintenance of existing bindings, or octane-react-library-port for a new port or copied and rewritten React implementation.

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

• Choosing the right workflow for Octane React library work
• Maintaining or auditing an existing binding
• Starting a new React implementation port

Assess Octane performance changes across runtime, compiler output, server rendering, hydration, scheduling, and bundle size. The skill helps choose a relevant benchmark, compare equivalent work against a baseline, investigate regressions, and report evidence and remaining uncertainty.

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

• Investigate a performance regression in an Octane change
• Choose benchmarks and metrics for a runtime or compiler update
• Assess bundle size, scheduling, or hydration costs