개발 스킬

Evaluate a proposed software change before implementation. It examines project files and official sources, compares options and trade-offs, and builds a concrete plan covering affected systems, effort, risks, and unresolved questions for the user's approval.

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

• Discuss a major change before implementation
• Compare migration or configuration options
• Estimate affected files and implementation effort

Review and test a pushed Factory branch before a pull or merge request is opened. Record findings against the exact tested commit, then approve the work or return it to the builder with actionable changes.

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

• Reviewing a branch before opening a pull request
• Checking whether earlier review findings were fixed
• Recording test results and required changes

Review a pull request by first forming an independent view of the problem and design. Investigate code, history, and evidence, then deliver a clear verdict, specific change requests, and a saved record for follow-up questions.

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

• Assessing the design and scope of a pull request
• Reviewing your own changes before sharing them
• Checking whether revisions resolve earlier findings

Investigate a GitHub issue or bug report by tracing code, checking relevant history, and testing the diagnosis where needed. Receive a concise verdict, supporting evidence, a proposed fix direction, and a record for follow-up questions.

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

• Triaging a newly reported bug
• Tracing the root cause of unexpected behavior
• Investigating a regression and its originating change

Coordinate multiple Mastra Code workers to investigate and fix GitHub issues in parallel. Keep each issue in a separate working directory, track progress in reports, review changes, and manage pull requests, reviewer feedback, and automated checks.

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

• Investigate and fix several GitHub issues in parallel
• Find issue candidates based on contribution history
• Track progress and blockers for each issue

Set up Herdr Kit and its Mastra Code integration, manage repository synchronization, and create or remove managed worktrees, separate working copies for review or development. The workflow checks supported operations and verifies the resulting manager state.

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

• Installing Herdr Kit and the Mastra Code integration
• Keeping repositories synchronized after closing their workspaces
• Creating or removing managed Review and Work worktrees

Turn a development goal into a focused ralph-loop command through conversation and codebase research. Define context, setup steps, ordered tasks, and testing criteria, then produce a complete command ready to copy.

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

• Turning a vague feature idea into concrete tasks
• Planning work around existing code patterns
• Defining build checks and completion criteria

Turn a Factory work item into a phased implementation plan grounded in current code and project history. Document scope, changes, tests, risks, and assumptions, then hand the plan to the execution stage.

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

• Planning implementation after issue triage
• Defining changes and verification for each phase
• Recording design choices and rejected alternatives

Write, review, or refactor React code using prioritized guidance for data fetching, bundle size, rendering, component structure, testing, and type safety. Start with high-impact issues such as sequential requests and unnecessary library loading.

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

• Writing React components and data-fetching logic
• Reviewing code for loading and rendering performance
• Refactoring large components and overly broad interfaces

Write, review, and refactor styles using Tailwind CSS v4 conventions. Consult guidance on CSS configuration, renamed classes, built-in styling features, and behavior changes when updating older v3 code or creating new styles.

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

• Updating Tailwind CSS v3 syntax for v4
• Defining colors and spacing through CSS configuration
• Reviewing classes and behavior changes

Build and update Mastra application interfaces using existing components from @mastra/playground-ui. Follow shared visual styles, arrange layouts with Tailwind utilities, and connect themes and stylesheets while avoiding duplicated components or unsupported appearance overrides.

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

• Building a new Mastra application screen
• Adjusting layouts with existing components
• Connecting shared themes and stylesheets

Review open Mastra GitHub issues and trace reported defects to source code. Apply the @mastra/core label to confirmed core bugs, report uncertain ownership, and summarize whether fixes are active, stale, or unclaimed.

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

• Checking whether reported bugs belong to @mastra/core
• Labeling confirmed core bugs with supporting evidence
• Previewing issue classifications without changing GitHub

Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.

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

• Checking whether previous review findings were addressed
• Finding regressions introduced by follow-up commits
• Re-running tests against the current PR head

Review code for performance bottlenecks across database queries, memory use, frontend rendering, network requests, and algorithms. Use a structured checklist to identify optimization opportunities and classify their severity according to expected load and scale.

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

• Reviewing database queries for avoidable overhead
• Checking memory leaks and unbounded resource growth
• Reviewing React rendering and long-list performance

Configure Factory board behavior and GitHub or Linear event handlers in deployment code. Adjust stage transitions, phase meanings, and tool-result handling, then check the changes with focused tests and versioned audit records.

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

• Add approval requirements to board transitions
• Change GitHub or Linear event handling
• Define custom board phases and tool-result rules

Draft and post GitHub pull request reviews and issue comments with precise locations, required changes, and supporting reasons. It checks the posting account, applies approval rules, and selects the appropriate review outcome.

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

• Draft a pull request review with actionable required changes
• Explain an issue's cause and requested fix
• Check posting approval and self-review handling

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

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

Split a large pull request into smaller, reviewable changes. Plan branch dependencies, extract related code, verify each part, and track review changes while preserving the intent of the original work.

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

• Split a large pull request into reviewable parts
• Separate refactoring from behavior changes
• Plan dependent pull requests

Review a pull request in a Factory work session by investigating its purpose, history, implementation, tests, and security. Publish verification results and a review verdict, then record the outcome on the work card.

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

• Reviewing a pull request assigned through Factory
• Checking whether a bug fix addresses the underlying cause
• Verifying findings from bots and human reviewers

Turn pull request changes, commits, and test evidence into a self-contained HTML guide. Explain the problem, system context, before-and-after behavior, and key code changes so reviewers know where to focus.

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

• Explain a complex pull request before review
• Show before-and-after behavior with diagrams
• Collect test evidence and review focus points

Query Herdr's Review Manager and Work Manager across repositories to recommend actionable pull requests. Compare review status, automated checks, size, and local state, and create local review checkouts for explicitly confirmed remote-only records.

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

• Choose the next pull request to review
• Find author follow-up work and failing automated checks
• Check local changes and stale manager records

Investigate difficult bugs by adding temporary logs to the actual execution path and reproducing the reported behavior. Analyze JSONL logs, which store one structured event per line, then fix the cause, verify regression tests, and remove debugging artifacts.

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

• Investigating bugs that occur only during manual use
• Tracing event order in streaming or concurrent operations
• Checking whether passing tests cover the reported bug

Re-review a GitLab merge request after new commits, track the outcome of every previous finding, and inspect both new changes and the full proposal. Verify the current code, then publish a test report and review verdict.

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

• Re-reviewing a merge request after fixes
• Tracking the resolution of earlier review findings
• Checking new commits for regressions and incomplete fixes