القائمة
Use this skill when you need to triage, draft, or improve a GitHub issue with strong repro steps and acceptance criteria; use runSubagent to gather evidence and pre-fill the issue.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when you need to diagnose and fix React 19 performance issues (render churn, slow updates, Suspense/Transitions, memoization, profiling, and React Compiler).
Write clean, behavior-focused unit/integration tests that remain trustworthy when code is written or modified by agents (prevents “test weakening”, enforces invariants, and adds CI guardrails).
Use this skill when you are creating or updating Agent Skills in your project (structure, YAML frontmatter, naming, and progressive disclosure).
Use this skill when designing or refactoring boundaries, responsibilities, and change drivers using practical software architecture “hard parts” thinking + SRP.
Use this skill when you need a Bun runbook (dev, build, lint, typecheck, tests, migrations, and verification steps).
Use this skill when you need a thorough code hygiene pass (dead code, lint escapes, consistency, formatting drift, and subtle smells) on touched files.
| name | quality-github-issues |
| description | Use this skill when you need to triage, draft, or improve a GitHub issue with strong repro steps and acceptance criteria; use runSubagent to gather evidence and pre-fill the issue. |
| allowed-tools | runSubagent, mcp_github_issue_read, mcp_github_issue_write |
Use this skill when you need to file (or help someone file) a GitHub issue that is easy to understand, easy to reproduce, and easy to validate after the fix.
This skill works well for modern web app stacks; adapt the stack details as needed:
/{locale}/...)A quality issue:
Search existing issues and PRs with a few keywords:
/en/(dashboard)/clients)/{locale}/... if your app uses locale prefixes)If it’s a duplicate, comment on the existing issue with your additional repro/context instead of creating a new one.
Do not paste:
If needed, redact values and keep structure (e.g. userId: "user_***").
Format (pick one):
Bug: <short symptom> in <area>Feature: <capability> for <persona/area>Tech: <component> <change>Good:
Bug: Client duplicates dialog crashes on empty lastNameFeature: Finalized invoice PDF uses immutable snapshotAvoid:
BrokenHelp!!!It doesn’t workUse this template in a new issue body.
One sentence describing what’s wrong / what you want.
Who is affected and how badly? (blocker / annoying / cosmetic)
Check all that apply:
What should happen.
What happens instead.
Provide the smallest reliable sequence:
If this is flaky/intermittent, describe frequency and any patterns.
Attach visuals if it’s UI-related.
Paste relevant logs/errors (redact secrets/PII). If it’s a Next.js error overlay, include the stack trace.
If this is a performance/cost issue, include (if you can):
revalidatePath on large paths)/{locale}/(dashboard)/...List verifiable outcomes. Example:
If it’s a perf/cost issue, add acceptance criteria like:
Links, code pointers, or hypotheses.
Include these when relevant:
actions/clients/mutations.ts)db/schema/...)/en vs /de)messages/en.json or messages/de.jsonUse runSubagent when you want help gathering evidence fast without making changes.
When you do want to interact with GitHub issues directly (instead of only drafting text), use whatever GitHub issue read/write tools you have available:
issue_read: fetch issue details, labels, comments, and sub-issues to confirm scope and avoid duplicates.issue_write: create a new issue or update an existing one (e.g., improve repro steps, add acceptance criteria, close as duplicate).If you’re using GitHub MCP tools, these may map to tools like mcp_github_issue_read and mcp_github_issue_write.
Good subagent tasks:
Provide:
Ask the subagent to return:
Use consistent labels (adapt to your project’s label set):
bug, feature, choreclients, projects, time, invoices, pdf, i18n, auth, dbp0-blocker, p1-high, p2-medium, p3-lowIf labels don’t exist yet, include your suggestions in the issue body.
A fix is “done” when: