メニュー
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description. Use when you have a bug report or failing test and want Claude to investigate and fix without step-by-step guidance.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | fix-bugs |
| description | Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description. Use when you have a bug report or failing test and want Claude to investigate and fix without step-by-step guidance. |
| license | MIT |
| compatibility | Designed for Claude Code. Works best with access to CI logs, Slack MCP, or docker CLI. |
| metadata | {"author":"rajit","version":"1.0"} |
| allowed-tools | Bash Read Grep Glob Edit Write |
Fix the bug described or linked. Do not wait for step-by-step instructions — investigate and fix autonomously.
User: fix this https://slack.com/archives/C07VBSH.../p1234
→ Claude reads Slack thread, finds the bug, fixes it
User: go fix the failing CI tests
→ Claude reads CI logs/test output, traces failures, patches code, reruns
User: look at these docker logs and fix whatever's broken
[paste logs]
→ Claude parses errors, finds the service + file, fixes it
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.
Act as a Senior Conversion Strategist to write complete website copy — hero, features, social proof, FAQ, and footer — with persuasion triggers, power words, and character counts. Use when writing or rewriting copy for a landing page, SaaS site, or product launch. Output populates directly into Figma Make layouts.
Run analytics queries against any database using plain English — BigQuery (bq CLI), PostgreSQL, MySQL, SQLite, or any DB with a CLI/MCP/API. Use when you need to pull metrics, analyze data, or answer business questions without writing SQL.
Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate. Use when you have a systems-architect, visual-system-architect, or conversion-copy output and need to convert it into Figma Make–compatible prompts covering hero, features, social proof, CTA, and mobile views.
Adversarial code review before a PR — Claude asks hard questions until you pass the test. Also supports elegant rewrites ("scrap this and implement the elegant solution") and spec-driven development. Use before opening any pull request.
Act as a Senior Frontend Systems Engineer to architect interactive modules — multi-step forms, pricing calculators, faceted search, dashboards, and auth flows. Defines state machines, data flow, error handling, and React component structure. Use when designing complex UI logic for Figma Make prototypes or React implementation.