개발 스킬

Investigate errors, failing tests, or slow behavior and explain the causal chain with source file and line references. Deliver diagnosis alone or apply a verified fix, starting with a test that reproduces the defect.

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

• Trace the cause of an error or failing test
• Investigate unexpectedly slow behavior
• Get a diagnosis before deciding on a fix

Address existing feedback on a GitHub pull request, a proposed code change. Evaluate comments against the code, apply valid fixes, and verify replies and thread resolution, with options for local handoff or resuming saved work.

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

• Addressing feedback across a pull request
• Handling a specific review thread
• Preparing local fixes for someone else to publish

Carry a request through the appropriate Compound Engineering skills with minimal intervention. For code changes, the workflow covers planning, implementation, review, browser testing, and an open pull request with automated check results assessed.

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

• Taking a feature request through to an open pull request
• Diagnosing a bug and preparing the fix for review
• Implementing an existing plan through delivery

Save working changes as local Git commits with messages that explain the outcome. Follow the project's commit style, select files explicitly, and split clearly separate changes into a few logical commits when appropriate.

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

• Saving completed work as a local commit
• Writing messages that explain the outcome
• Separating unrelated changes into commits

Commit and push code changes, then open a pull request with a clear title and description. You can also draft or update PR descriptions and hand published requests to the follow-up monitoring workflow.

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

• Committing changes and opening a pull request
• Drafting only a PR title and description
• Updating an existing PR description

Review code changes or a pull request for bugs, effects on existing behavior, test gaps, and project standards. Receive findings supported by the code and a clear account of review coverage, with local fixes available when explicitly requested.

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

• Reviewing a pull request before release
• Checking changes for bugs and test gaps
• Applying review findings locally

Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.

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

• Clarifying a vague feature idea
• Narrowing the scope of an ambitious improvement
• Documenting requirements before implementation planning

Set up a separate Git working directory for a new task or an existing branch, pull request, or commit. Detect and reuse existing isolation, prefer the agent environment's worktree tools, and report the working path and branch.

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

• Starting a feature in a separate working directory
• Isolating an existing branch or commit
• Preparing a separate workspace for pull request review

Review Pascal pull requests or branches against documented architecture rules. Check package responsibilities, node extension patterns, state management, and rendering subscriptions to identify misplaced code, compatibility breaks, and changes that could cause excessive redraws.

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

• Reviewing a Pascal pull request for architecture violations
• Auditing package responsibilities in a branch
• Checking new node definitions and scene compatibility

Create or update a pull request from the current branch using its actual commits and changes. Fill the repository template with a concrete description, reviewer test steps, and accurately reported checks, then push the branch.

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

• Opening a pull request from the current branch
• Updating a pull request after additional changes
• Writing reviewer test steps from the actual changes

Turn rough bug reports, feature requests, support notes, or pull requests into concise issues. Explain the current problem and desired behavior in plain language, preserving useful evidence without prescribing how developers should implement a solution.

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

• Simplifying a lengthy bug report
• Drafting an issue from a pull request
• Clarifying the intended experience for a new feature

Prepare a development branch for final maintainer review by checking security, unnecessary complexity, and billing abuse risks. Fix confirmed issues, run local checks and tests, then push changes and create or update the pull request.

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

• Preparing a feature branch for final review
• Checking security and billing abuse risks
• Simplifying unnecessarily complex changes

Prepare an OpenSEO release by updating the version, selecting user-visible changes from commits, and writing concise release notes. Review agents check the draft against the code before a pull request is opened for the release.

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

• Prepare an OpenSEO release pull request
• Summarize changes since the previous release
• Update the version and release notes together

Review a pull request, a proposed code change, for code that can be removed or simplified. Consider product decisions, final functionality, and whether rare edge cases have led to unnecessary complexity.

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

• Review a pull request for simplicity
• Find code that could be deleted
• Reconsider overcomplicated handling of rare cases

Create or update skills using OpenSEO's repository conventions. Keep one canonical source, distinguish internal and public workflows, maintain Claude Code links, and register public skills in documentation, the in-app agent, and plugin bundles.

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

• Add a new skill to the OpenSEO repository
• Turn a development workflow into an internal skill
• Repair drift between skill directories

Create a concise review brief for a branch or pull request. Show critical code, before-and-after behavior, risks, test status, and commands to try the change, helping maintainers focus their review on consequential decisions.

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

• Understand a pull request's key changes quickly
• Locate code that needs careful review
• Compare behavior before and after a fix

Record recurring setup and workflow problems that a repository can fix, so future contributors can avoid the same friction. Also review existing entries, remove duplicates, prioritize useful fixes, and preserve a history of resolved problems.

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

• Recording confusing setup steps
• Tracking recurring problems in repository scripts
• Deduplicating and prioritizing friction reports

Trace application behavior and explain data structures using compact text tree diagrams. The diagrams connect user actions to real functions, data types, state changes, and the components that render again as a result.

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

• Tracing what happens after a user action
• Investigating why a component renders again
• Mapping data structures and their consumers

Set up and run Happy components locally, including its CLI, server, mobile app, and desktop app. The guide covers building, testing, checking logs, and separating development data using pnpm, the project's package management tool.

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

• Setting up a local Happy development environment
• Rebuilding the CLI and checking its daemon
• Running the server and app locally

Search past coding sessions across Claude Code, Codex, and Cursor to recover earlier attempts, failed approaches, decisions, and findings. It filters history by topic and time, then summarizes technical details relevant to the question.

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

• Recovering approaches tried in earlier sessions
• Reviewing past debugging attempts and failures
• Summarizing recent work across coding agents

Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.

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

• Grouping open issues and identifying duplicates
• Checking whether reported bugs are fixed on main
• Drafting replies and issue closure comments

Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.

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

• Connecting browser tools to a local Electron development app
• Inspecting screen state during debugging
• Entering a task in the composer and running it

Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.

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

• Registering a feature before implementation
• Releasing a feature to selected organizations
• Separating cloud and self-hosted availability

Review changed UI code against numbered rules in DESIGN.md. Findings identify the relevant rule, affected lines, and a small fix for issues such as wording, component reuse, visual styling, accessibility, or missing screenshot evidence.

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

• Checking UI changes against documented design rules
• Reviewing button labels and access restriction messages
• Spotting inconsistent components, colors, and motion