개발 스킬

Triage a GitHub issue by reviewing its discussion, related issues, and fixing pull requests. Publish a concise comment with classification, severity, evidence, and the next action, then update a small set of triage labels.

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

• Classifying newly opened GitHub issues
• Requesting missing reproduction details
• Identifying duplicates and existing fixes

Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.

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

• Investigating the root cause of a reported bug
• Checking for duplicate issues or regressions
• Preparing findings for whoever plans the fix

Design instructions for agents that write, fix, review, or refactor code. Define behavior based on file access, select suitable tools, and set clear verification and completion rules for repository changes or copyable code output.

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

• Designing an agent for repository bug fixes
• Defining a pull request review agent
• Creating a code generator without workspace access

Write Git commit messages that preserve why changes were made. The skill keeps Conventional Commits subject lines and adds structured body entries for user intent, decisions, rejected alternatives, constraints, and lessons supported by the session context.

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

• Recording the purpose behind a feature
• Preserving design decisions and rejected alternatives
• Documenting constraints and implementation lessons

Develop and maintain the WXT browser extension that adds a Repomix button to GitHub repository pages. The skill covers Chrome, Firefox, and Edge compatibility, extension scripts, translation files, and commands for building, linting, and testing.

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

• Maintaining the GitHub Repomix button extension
• Checking Chrome, Firefox, and Edge compatibility
• Updating translations or adding a language

Combine code from local directories or GitHub into one structured file for AI analysis. Examine project structure, search for related code, and check estimated tokens, the units AI models use to process text.

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

• Preparing a single codebase file for AI analysis
• Reviewing a project's directory structure
• Finding authentication code and database models

Explore local or remote repositories with Repomix CLI to understand their structure, locate related code across files, and review file counts and estimated tokens, the units AI models use to process text.

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

• Understanding an unfamiliar project's structure
• Locating authentication code and API endpoints
• Checking file counts and estimated AI tokens

Configure Crush with Bash or JSON files to choose AI providers and models, connect external tools, set permissions, and adjust behavior. Understand how project and global settings combine when customizing your working environment.

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

• Set up AI providers and model selections
• Connect MCP servers and language servers
• Configure tool permissions and execution hooks

Create, configure, and troubleshoot Crush hooks, commands that run before tool execution. Use them to block or approve calls, rewrite tool input, or add context for the agent, with guidance on configuration and troubleshooting.

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

• Blocking destructive shell commands
• Automatically approving read-only tools
• Adding editing reminders for the agent

Extract fields, filter records, and reshape JSON from API responses, configuration files, or logs using Crush’s built-in jq. Get help writing and debugging transformations, constructing new JSON, and formatting output for other commands.

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

• Extract selected fields from API responses
• Filter JSON arrays by conditions
• Reshape configuration data or construct JSON

Add or edit skills bundled with Crush, following guidance on file placement, required metadata, compile-time embedding, and discovery tests. It also explains how built-in skills are loaded and how user skills override them.

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

• Adding a skill bundled with Crush
• Editing an existing built-in skill
• Understanding skill discovery and overrides

Add or modify commands handled inside Crush's embedded shell before they reach the operating system. The guidance covers command routing, input and output streams, exit codes, and cancellation so commands work with pipes, redirection, and hook timeouts.

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

• Adding a command to Crush's embedded shell
• Modifying an existing built-in command
• Supporting pipes and output redirection

Turn recurring lessons in Claude's automatic memory into concise project rules. Choose a project-wide, file-specific, or personal rule location, include concrete commands, and clean up the original memory entry after confirmation.

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

• Make repeated corrections into lasting rules
• Record the project's package manager
• Apply API rules to selected file paths

Turns recurring workflows and proven debugging solutions into reusable skill packages. It creates SKILL.md, a readable overview, and optional supporting examples from a user description or saved project memory, with checks for completeness and portability.

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

• Saving a debugging solution as a reusable skill
• Packaging recurring workflows for other projects
• Turning saved project knowledge into documented procedures

Generate a starting project for a subscription web app with Next.js, including sign-in, database schemas, billing routes, and a dashboard. The workflow also covers staged validation and reference documents for customization and common setup problems.

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

• Starting a subscription web app
• Setting up authentication and billing together
• Building a dashboard and pricing page

Turn a written app specification into a runnable starter project using the requested technology stack. Generate implemented features, tests, configuration files, and setup instructions, then check the project for common omissions.

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

• Turning a requirements document into a starter project
• Creating a task API with FastAPI and SQLite
• Building a recipe-sharing website with Next.js

Turn plain language requirements into SQL, investigate slow queries, document database structures, and prepare migration templates with rollback plans. Support everyday database development and ORM use, where libraries connect application code to database tables.

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

• Writing SQL for reports and data retrieval
• Investigating slow queries and repeated database calls
• Preparing schema changes and rollback plans

Track code changes in structured JSON records, including reasons, test results, progress, and approvals. Save remaining tasks and key decisions so another AI session can understand the work and continue from the recorded handoff.

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

• Handing unfinished work to another AI session
• Recording why code changed and how it was tested
• Reviewing progress and approvals for each change

Investigate slow Node.js, Python, and Go applications by measuring CPU use, memory, database queries, and data transfer. Identify bottlenecks, inspect frontend bundle sizes, run load tests, and compare measurements before and after changes to verify improvements.

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

• Investigating slow API responses
• Tracking memory growth and suspected leaks
• Analyzing bundle growth after adding dependencies

Turn a Markdown code review into a single HTML file with code changes beside severity-labeled comments. Readers can jump to findings, inspect line numbers, and identify the named human reviewer.

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

• Turning a lengthy Markdown code review into HTML
• Reading code changes beside review comments
• Jumping directly to findings by severity

Scan a codebase for technical debt—issues that make future maintenance harder—and prioritize fixes using business impact and effort. Generate a ranked backlog, sprint allocations, and trend reports to assess cleanup work over time.

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

• Assess technical debt across a codebase
• Prioritize refactoring for the next sprint
• Compare debt levels before and after cleanup

Review GitHub pull requests and GitLab merge requests for security, test gaps, compatibility, and performance risks. Trace affected code and services, then produce a prioritized report with suggested fixes and a structured review checklist.

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

• Reviewing shared libraries and API changes before merging
• Organizing feedback on large pull requests
• Checking authentication and payment code changes

Plan features before coding by defining requirements, acceptance criteria, and scope. Validate the specification, generate starter tests from expected behaviors, and guide implementation and review so each delivered feature can be checked against its agreed requirements.

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

• Define requirements before implementing a feature
• Turn acceptance criteria into starter tests
• Check specifications for missing requirements

Manage multiple apps and shared packages in one repository. Analyze dependencies and change impacts, limit builds and tests to affected packages, configure caching, and plan repository consolidation while preserving Git history.

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

• Checking which apps a shared package change affects
• Limiting CI builds and tests to affected packages
• Combining repositories while preserving Git history