개발 스킬

Use the shared design system when building or styling the React dashboard and Docusaurus website. It explains theme tokens, reusable components, page patterns, accessibility, and visual checks so frontend changes stay consistent across light and dark modes.

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

• Adding a dashboard page or component
• Styling or fixing a website page
• Checking theme tokens and accessibility patterns

Implement Go features from a spec or plain-language request using a test-first workflow. It guides you through identifying affected files, writing integration tests, following project patterns, and verifying the result in the devcontainer.

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

• Adding a CLI command or flag
• Building a feature from a spec
• Creating an internal Go package

Run Skillshare CLI commands, Go tests, debugging, and the web dashboard inside the Linux devcontainer. The workflow keeps verification on the project's intended platform, supports isolated test homes, and picks up source edits without a manual rebuild.

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

• Run Skillshare CLI checks in the Linux container
• Execute Go unit or integration tests
• Reproduce a bug using an isolated home

Get guidance on DataChain SDK APIs, method signatures, UDFs, and Python code patterns when no particular dataset or bucket is involved. It provides the rules needed to write pipeline code, including saving and exporting data.

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

• Checking a DataChain method signature
• Writing a DataChain UDF
• Asking about SDK code patterns

Clean up code after tests pass by simplifying logic, removing dead code, and improving names while preserving behavior. Use it as the refactoring step in a test-driven workflow to make code easier to read and maintain without adding features.

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

• Simplifying code after implementation tests pass
• Removing dead code or needless indirection
• Cleaning up code before a pull request

After `/write-tests` creates failing tests, inspect them to understand the requirements and add only the code needed to pass. Run tests as changes are made, and stop when the suite passes without adding unrelated features or refactoring.

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

• Implement behavior required by failing tests
• Make focused changes after a `/write-tests` run
• Complete the green phase of a TDD cycle

Turn a GitHub issue into a focused development workflow: extract its goal and acceptance criteria, create an isolated worktree, enable TDD checks, and begin writing tests for the first requirement.

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

• Start focused work on a GitHub issue
• Keep issue changes isolated in a worktree
• Begin test-driven development from acceptance criteria

Monitor a pull request's CI checks and Greptile code review. The skill waits for results, helps address failures and actionable comments within set iteration limits, and reports whether the PR is ready for human review or still needs attention.

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

• Monitoring CI after submitting a pull request
• Checking for Greptile review comments
• Addressing CI failures and iterating on fixes

Coordinate work on several GitHub issues in parallel, creating a separate worktree and enabling test-driven development for each. A lead agent tracks conflicts and orders the completed changes into stacked pull requests, with a setup-only fallback when Agent Teams are unavailable.

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

• Batching several small or medium GitHub issues
• Working on independent issues in parallel
• Preparing worktrees when Agent Teams are unavailable

Assess whether a proposed change needs an RFC, a document for discussing design decisions. Review changed files, public API changes, new patterns, and related RFCs, then report a verdict with reasoning and suggested topics to document.

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

• Checking whether a new API needs an RFC
• Reviewing a breaking change before implementation
• Assessing a major architectural decision

Check whether changes are ready for a pull request by reviewing branch freshness, lint, tests, debug code, project principles, RFC needs, and documentation. The result is a report of blockers, reviewer discussion points, and an overall readiness verdict.

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

• Checking changes before opening a pull request
• Finding blockers when asked if code is review-ready
• Reviewing API changes for RFC and documentation needs

Turn a concrete use case into a new OpenEnv environment. The workflow researches the target library or API, selects relevant examples, settles key design choices, and builds typed models, client and server code, and the environment manifest.

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

• Creating an OpenEnv environment for a library
• Wrapping an API as an agent environment
• Choosing actions, observations, rewards, and episode settings

Review code changes for mechanical defects and alignment with OpenEnv principles and RFCs. It runs lint and debug checks, then reports immediate fixes separately from design concerns that need reviewer discussion, including conflicts with open RFCs.

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

• Reviewing a pull request for bugs and design fit
• Checking changes before committing
• Finding debug code, lint failures, or missing imports

Use the `openenv` command-line tool to scaffold a new OpenEnv environment, validate a project, build it, and push it. The skill gives the basic commands and points to help for options specific to each command.

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

• Create a new OpenEnv environment scaffold
• Validate an OpenEnv project before building
• Build and push an OpenEnv environment

Use this skill to turn a TLA+ system model or an agreed Mermaid chart into a state diagram people can review. It labels states and transitions in reader-friendly terms, shows rule-breaking paths, and supports checking modeled bugs against code or refining a design before implementation.

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

• Showing a bug as a sequence of system states
• Reviewing product, protocol, or service behavior with a state diagram
• Checking a TLA+ model against existing code

Coordinate a product change across the places that describe or consume the same fact, including code, documentation, and user-facing copy. Identify every affected surface, reduce duplicated information, and add checks or paired changes where systems share a format.

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

• Adding or renaming a user-facing feature
• Updating product copy and documentation
• Renaming a serialized response field

Plan Python library releases with semantic versioning and a structured changelog. The skill covers release automation with GitHub Actions, deprecation warnings, and steps for communicating breaking changes and checking a published release.

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

• Choosing a version number for a library release
• Writing and organizing a project changelog
• Automating builds and publishing with GitHub Actions

Verify how an external library, API, build backend, or scraped page behaves before relying on it. Use quick probes against the exact call or service, inspect real requests and responses, validate fakes, and check that dry-run modes do not skip the failing step.

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

• Integrating a new library or API endpoint
• Checking a tolerated status or error-handling branch
• Verifying client argument names and request parameters

Use this skill to find secrets and development clutter in Git tracking, prevent them from being committed, and clean up files already present. It explains how ignore rules differ from untracking, when credentials need rotation, and how verification can create new artifacts.

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

• 新しいリポジトリの除外ルールを整えたいとき
• 追跡中の秘密情報や生成物を監査したいとき
• コミット済みの.envを追跡対象から外したいとき

Build and test Python MCP servers with FastMCP, which exposes tools to LLM clients. Design predictable errors, safely wrap command-line tools, keep blocking work from stalling requests, and avoid packaging and testing pitfalls.

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

• Creating an MCP server that exposes Python tools to an LLM client
• Wrapping a command-line program for use through MCP
• Debugging tool registration or package distribution

Review ffmpeg-skill changes by tracing result claims to what the tools actually measured, checking contract and documentation coverage, tests, dependencies, and project boundaries. Findings include the affected file, concrete failure, and smallest useful fix.

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

• Reviewing a pull request or diff in ffmpeg-skill
• Checking a change before committing it
• Assessing an external audit or review report

Resolve common conflicts when several branches change the same repository. The skill explains when to combine entries, recalculate shared values, or rebuild generated files, and how to check the merged result before pushing.

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

• Resolving conflicts while rebasing or merging a long-lived branch
• Reviewing a merge commit for lost or shadowed changes
• Deciding which repository files should be generated

Explore a codebase and explain how a feature or subsystem works, how runtime steps connect, and where code belongs. It creates a concise architectural walkthrough for onboarding or before making changes, using subagents for larger questions.

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

• Understand how a feature or subsystem works
• Trace runtime flow before changing code
• Find the right package or architectural layer for new code

Use this skill when designing types or reviewing function signatures in statically typed code. It helps distinguish values that share a primitive representation, parse untrusted input at system boundaries, handle every variant, and derive types from the schema that defines the data.

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

• Distinguishing IDs or values that share the same primitive type
• Parsing JSON, configuration, or database input into typed models
• Checking that every variant is handled