Каталог навыков агентов

You are an expert code reviewer. Your role is to independently review fix plans produced by another agent and identify i...

8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the te...

Diagnose bugs through iterative investigation, apply a type-safe fix, and generate a regression test. Use when asked to...

用证据、受控假设和已验证修复来诊断并修复已观察到的缺陷，避免猜测式改动。

Advanced diagnostic workflow for bug-fixer agent with mandatory Context7 MCP consultations, Chrome DevTools MCP integrat...

Diagnose a reproducible defect, make the smallest repair, and prove the repair.

Systematic debugging workflow for CircleTel - analyzes errors, identifies root causes, proposes fixes, and validates sol...

Adaptateur Claude/Cline vers la skill canonique de correction HIVMeet.

Systematic debugging and bug fixing with Australian user-friendly messages

Diagnose bugs through evidence, hypotheses, reproduction paths, and targeted fixes.

Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusin...

Summarizes the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing attempts,...

Systematically debug issues using Sherpa's Bug Hunt workflow. Activates when fixing bugs, investigating errors, debuggin...

Launch a swarm of bug-hunting agents against a target file, module, or topic.

Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "fai...

Proactive bug-hunting workflow. Assesses codebase risk through complexity, coverage, and structural analysis, then spawn...

Use when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as inte...

Find bugs in frename before the owner does, UI bugs first. Use in every nightly session (step "Bug hunt" of the nightly...

Use when an unknown crash, intermittent failure, or cross-subsystem bug needs parallel read-only reproduction lanes, ran...

Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained f...

Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fi...

Copilot agent that assists with bug investigation, root cause analysis, and fix generation for efficient debugging and i...

Specialist bug and weakness hunter for any codebase: logic errors, edge cases, error handling, races, data integrity, co...

Use when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs....

Bug 修复影响分析：判断根因是否真被解决、修复是否引入副作用、影响范围与回归风险。触发："分析这个 bug 的影响"、"这个修复会影响什么"、"评估修复风险"、"bug impact analysis"。

Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "...

[バグ対応] 2. トラブルシューティング調査実行と仮説の絞り込み

Systematic bug investigation and root cause analysis

Test-first bug investigation workflow. Use when user reports a bug, error, unexpected behavior, mentions "something is b...

Diagnose and fix software bugs through evidence-based investigation. Use when Codex needs to handle runtime errors, fail...

Executes diagnostic investigation tasks to test debugging hypotheses. Runs tests, traces execution, checks git history,...

Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use when asked to "fix this bug", "deb...

Identify the precise location of bugs in source code, modules, and systems. Use this skill when debugging applications,...

Curated edge case test data for boundary testing, verification scripts, and test generation. Provides pre-curated refere...

[バグ対応] 1. トラブルシューティングログ生成

[バグ対応] 3. トラブルシューティング修正策で仮説→合理的な修正策の列挙

Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or reco...

Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.

Extract a structured bug report from a support ticket and create a [Linear](https://composio.dev/toolkits/linear) issue.

Use when a defect needs structured documentation, reproduction steps, severity assessment, verification, or closure.

Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug repor...

Turns a Larch Tasks user complaint into a reproducible bug ticket. Use when asked to "file a bug", "write this up as a t...

Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report...

Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report...

创建结构化 Bug 报告技能。收集复现步骤、环境信息、预期与实际行为，生成符合项目模板的 Bug 报告文件并登记到 Bug 列表。

Reproduce a user, customer, or support-reported problem with synthetic data, prove the cause with a temporary test, reco...

Builds a well-formed bug (defect) report from raw observation notes - fills in summary, environment, steps to reproduce,...

Use when writing or improving a bug report, defect ticket or Jira/GitHub issue from notes, screenshots, logs, a video de...

Use when any case fails or you reject a criterion - what goes in the review_criterion note, the failed case and the numb...

Capture bug context, generate reports, and optionally create GitHub issues or share patterns

Write high-quality bug reports that engineers can reproduce and fix without back-and-forth. Apply structured format with...

Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated too...

Use this skill when you need to write clear, reproducible bug reports with steps, environment details, and evidence; tri...

Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or esta...

Turn a vague bug report or a long failing script into the smallest reliable reproduction: reduce it to a single command...

Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and...

Turn a reported defect into a reliable, minimal, evidence-backed reproduction with exact environment, preconditions, ste...

Turn bug reports into reproducible steps and diagnostic plans. Use when Codex is asked to reproduce a bug, reduce a flak...

Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end...

Use when turning Chinese bug reports into minimal reproducible examples, environment checks, regression ranges, and main...

Create minimal reproduction tests from bug reports and error descriptions. Use when writing failing tests from bug repor...

Reproduce bugs and gather evidence for root cause analysis. Use when investigating a bug report to confirm reproduction...

Resolves selected ClawPatch findings through classification, bounded fixes, triage, docs/debt routing, and revalidation....

- Quick Start

Diagnose a specific non-CI runtime bug by first qualifying a repeatable success/failure signal, then using minimal repro...

Turn a free-text bug description into a paste-ready ticket stub — a short title and a one-paragraph summary — with no co...

Codebase bug hunt: fix AI-fixable bugs, defer the rest.

Methodically walks a running app — every public route, every interactive control, every state (empty/loading/error/auth/...

Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces. Use this skill w...

Internal helper invoked only by other skills in this plugin (bug-submit, bug-fix) to (re)generate the repo-wide bugs/bug...

Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.

Create a bug triage with structured process, quality checks, and system integration

Triage and fix GitHub bug reports for Aries AI. Use when a GitHub issue is classified as a bug, regression, defect, outa...

Use when open game bugs need priority and severity review, sprint assignment, or systemic trend analysis.

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends...

Reproduce, isolate, and fix a bug (or failing build/test), then summarize root cause, fix, and verification steps. Use w...

Triage a reported defect or incident by setting severity, reproducing it, ranking evidence-backed hypotheses, identifyin...

Use when a bug arrives from outside the team, before debug: turn a report into a reproducible case with an evidence trai...

Turn a pile of bugs, issues, and error reports into a ranked, actionable plan with reproduction evidence. Triggers: you...

Bug 重新优先排序技能。读取所有未解决 Bug，按严重度、影响面、紧急度重新排序，输出分流建议与处理路径分配。

Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environmen...

Triage bug reports by severity, recommend fix order, generate client communication templates, determine whether to charg...

Systematically explore and test any software project (CLI, API, Backend, Library, etc.) to find bugs, usability issues,...

Analyze Cursor Bugbot PR comments through a root-cause lens: is the finding valid, and is the suggested fix the real fix...

Automate Bugbug tasks via Rube MCP (Composio). Always search tools first for current schemas.

Write Bugcrowd-format reports — VRT (Vulnerability Rating Taxonomy) mapping, P1-P5 severity, impact-led writing, and Bug...

Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exac...

Fix a reported bug with a regression test. Invoke with a bug description and reproduction steps.

End-to-end bugfix workflow — analyze environment (local Docker or cloud production), collect evidence, prepare bug repor...

Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use w...

Create and manage non-urgent bugfix branches in a git worktree with standard PR workflow (squash merge).

Structured debugging process for bug fixes: reproduce, plan, fix, verify. Use when fixing bugs.

Investigates and fixes bugs systematically with root cause analysis. Use when asked to debug, troubleshoot, fix a bug, i...

Lightweight bug-fixing loop — reproduce → root-cause → fix test-first → verify — deliberately separate from the heavywei...