개발 스킬

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

Sort issues and external pull requests, which are proposed code changes, by category and readiness. Verify reports, identify missing information, and record clear briefs so an agent or a person can take the next step.

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

• Finding issues that need a maintainer's attention
• Checking a bug report or an external pull request
• Preparing a clear brief for an agent to work from

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

Clarify a project's business concepts and terminology through concrete scenarios and comparisons with code. Record agreed definitions in a glossary and document significant design trade-offs in ADRs, records explaining why a decision was made.

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

• Resolving ambiguous business terms
• Creating or updating GLOSSARY.md
• Checking whether code matches business definitions

Write a pull request description that helps reviewers understand a code change. Use a compact diagram or diff, show before-and-after evidence, and explain how reversible the change is and what areas it may affect.

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

• Writing a pull request description
• Explaining a refactor with a file tree or diff
• Presenting before-and-after evidence for a UI change

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

Turn a course plan into numbered exercise folders with problem, solution, and explanation variants. Create starter readme files, check naming and links with the project’s linter, and fix structural errors before committing.

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

• Set up exercise folders for a new course section
• Create problem, solution, and explanation stubs
• Renumber exercises and check their structure

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

Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.

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

• Choosing a workflow from idea to implementation
• Finding the right starting point for bug investigation
• Planning a build that spans multiple sessions

Check skills before distributing them to Codex or Cursor. Identify unsupported metadata fields, Claude-specific variables in shell examples, and inconsistencies between source skills and their installation copies using the project's compatibility checker.

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

• Check a new skill before opening a pull request
• Review skill copies for Codex or Cursor
• Investigate compatibility findings from CI

Set up Everything Claude Code skills and hooks in DeepSeek Harness. Covers linking skill folders, generating hook settings, checking that hooks run, updating the setup, and investigating missing skills or inactive hooks.

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

• Install ECC skills in DeepSeek Harness
• Connect ECC hooks to a DSH profile
• Investigate missing skills or inactive hooks

Audit a focused part of an existing codebase, reconstruct its behavior and past decisions, and record gaps in reasoning, coding practices, features, and technology choices. Use the findings to plan, test, implement, and verify improvements.

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

• Review an inherited codebase
• Adopt the ECC engineering workflow midway through a project
• Rethink a module before adding more features

Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.

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

• Map callers and tests affected by an API change
• Review database migration and recovery plans
• Check authentication changes across modules

Design and review Java database code using MyBatis and MyBatis-Spring. Covers mapping query results to objects, safe SQL parameters, transactions, pagination, batch writes, and investigating slow or unnecessarily repeated queries.

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

• Designing mapper interfaces and XML mappings
• Reviewing dynamic SQL and parameter safety
• Checking transactions across multiple updates

Turn Git changes into a clear commit message using Conventional Commits, a format that labels the change type and optional scope. Review repository history to match its conventions, and flag unrelated changes that should be split.

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

• Drafting a message before committing
• Reviewing or correcting an existing commit message
• Writing a commit-style summary for a pull request

Turn Claude Code sessions into reusable working rules with evidence and confidence scores. Keep project-specific habits separate, share general patterns across projects, and group learned rules into skills, commands, or agents for repeated tasks.

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

• Learning recurring preferences from Claude Code sessions
• Keeping coding conventions separate for each project
• Turning learned rules into skills or commands

Apply shared coding conventions to new modules, reviews, and refactoring. Guides descriptive naming, readable structure, updates that preserve existing data, and error handling, giving teams a consistent basis for checking code quality.

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

• Setting coding conventions for a new project
• Reviewing code readability and maintainability
• Refactoring duplication and deeply nested logic

Design and review REST APIs, interfaces that exchange resources over HTTP, with consistent URLs, responses, and error handling. Covers pagination, authentication, request limits, and versioning to clarify how clients interact with an API.

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

• Designing new API endpoints
• Reviewing existing API contracts
• Adding pagination, filtering, and sorting

Plan database structure changes and existing data updates for production systems. Provides migration patterns for adding columns and indexes, switching applications in stages, and documenting recovery steps while accounting for downtime and database locks.

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

• Adding columns or indexes to production tables
• Updating large datasets in batches
• Planning a staged column replacement without downtime

Structure server-side applications with practical patterns for Node.js, Express, and Next.js API routes. Covers API design, database queries, caching, authentication, error handling, and background jobs, with examples that separate business rules from data access.

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

• Designing APIs and separating server responsibilities
• Reducing unnecessary database queries
• Adding caching and background jobs

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

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

• Diagnosing repeated failures in an agent run
• Investigating loops through the same tool calls
• Reviewing output degradation as context grows

Build or review Java Spring Boot backends using examples for web APIs, separate application layers, and database access. Covers input validation, error handling, caching, background processing, and logging to guide maintainable implementations.

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

• Designing web APIs and separating application layers
• Reviewing database access and transactions
• Adding input validation and centralized error handling

Design local data storage in Swift using actors, which control concurrent access to shared data. Combine an in-memory cache with JSON file storage, implement save and lookup operations, and connect the repository to an observable ViewModel.

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

• Building local storage for an iOS or macOS app
• Designing local storage for an offline-first app
• Replacing lock-based synchronization with Swift actors