스킬 찾기

Create and review Mastra tests that reproduce user-visible failures through public APIs, real network requests, and actual storage. Verify that tests fail before a fix and cover the different execution paths affected by the bug.

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

• Reproduce a reported bug before fixing it
• Review tests that rely heavily on mocked dependencies
• Check regression coverage across engines and adapters

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

Publish a Mastra preview package from a pull request or branch. Check the exact commit, confirm publication, monitor the release workflow, and report verified npm tags with a ready-to-copy installation command.

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

• Publishing a preview package from a pull request
• Sharing a branch build under a custom npm tag
• Checking publication results and installation commands

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

Create a dedicated test project linked to the current worktree and check Agent Builder through APIs and browser interactions. It covers agent and skill management, permissions, defaults, and related features, with selectable test sections.

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

• Validate an Agent Builder feature branch before review
• Check role-based permissions and authentication
• Test agent and skill management through APIs and the UI

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

Test mastracode’s terminal interface in Konsole, covering model setup, conversation switching, task state isolation, and display issues. The guide combines interactive checks with scripted rendering tests and troubleshooting steps for common build and configuration problems.

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

• Checking task state when switching conversations
• Setting up OpenRouter for interactive tests
• Testing borders and wrapping at different terminal widths

Create and improve Playwright end-to-end tests for Studio changes. Check complete user actions, including whether settings affect requests, data survives reloads, tools return expected results, and workflows pass data correctly.

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

• Testing whether agent settings affect actual requests
• Checking that saved data survives page reloads
• Verifying tool outputs and workflow data flow

Run smoke tests, or basic operational checks, for Mastra projects locally or in staging and production. Verify Studio screens, agents, tools, workflows, traces, and memory, then report results, blockers, and skipped checks.

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

• Checking a local Mastra project before release
• Testing Studio and server deployments in the cloud
• Running targeted checks for agents or traces

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

Create a Mastra project at a specified version and check its Studio in Chrome. Test page loading, agent chat, tool execution, and workflows, then report passed and failed checks, encountered errors, and screenshots.

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

• Checking a newly created Mastra project
• Testing initialization with a specified version or package manager
• Checking Studio chat, tools, and workflows

Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.

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

• Check retries and message changes after API errors
• Diagnose empty output in streaming tests
• Verify unrelated errors pass through unchanged

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

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

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

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

Provides a consistent process for open-ended tasks involving files, shell commands, or the web. Clarifies the goal, outlines steps before execution, reports progress, and finishes with a summary of changes, verification, and unresolved work.

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

• Organizing an open-ended request into concrete steps
• Checking existing files before creating new ones
• Following progress through step-by-step outcome reports

Researches questions on the web and produces a concise answer with source links. Saves useful URLs and short quotations in a Markdown notes file, keeping findings available in the workspace for later reference.

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

• Answering questions with web sources
• Saving research links and quotations in workspace notes
• Delivering an answer with sources and a notes file path

Review code for security vulnerabilities using a checklist covering unsafe input, authentication, access permissions, secrets, and data exposure. Classify findings into four severity levels to distinguish exploitable flaws, issues needing investigation, and smaller improvements.

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

• Review SQL, shell commands, and HTML for unsafe input
• Check authentication and access permissions
• Find exposed credentials and sensitive log data

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

Design agents that draft blog posts, social posts, newsletters, and marketing copy. Define the audience, brand voice, length, and required output so each agent delivers a complete draft with a headline and supporting notes.

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

• Build a blog writing agent with a consistent brand voice
• Design an agent for LinkedIn product posts
• Define delivery rules for newsletter drafts

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