메뉴
Refines GitHub issues using the block template and label table below. Tracking lives on GitHub; use when triaging issues, refining a new issue, or when the user asks to refine an issue.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Creates a GitHub PR for the current work using GitHub MCP; links to an existing issue with Closes
Checklist for updating project skills when the codebase or workflow changes. Use when applying the skill-maintenance rule, after dependency upgrades or script/e2e/release/issue-format changes, or when the user asks how to keep skills up to date.
Cross-language code quality principles for review and refactors. Use when reviewing structure and naming, applying Kent Beck-style patterns, or when working with the code-quality dev agent. Canonical text lives under .agents/.
Adds or updates extension E2E tests using the project Playwright setup and fixture (load unpacked extension, popup/background). Use when adding e2e for a feature, fixing failing e2e, or when changing popup/options/background flows.
Provides project context for the amgiflol WXT + Svelte 5 browser extension. Use when adding or editing extension code, adding entrypoints, fixing extension bugs, or when working in src/entrypoints or wxt.config.ts.
Uses changesets for versioning and changelog; avoids manual version bumps; aligns with build/zip and workflow_dispatch. Use when cutting a release, adding a changeset, preparing for publish, or when touching version or changelog.
| name | issue-refinement-triage |
| description | Refines GitHub issues using the block template and label table below. Tracking lives on GitHub; use when triaging issues, refining a new issue, or when the user asks to refine an issue. |
Use GitHub issues for open/closed tracking and descriptions. This file defines the label table and issue block template only.
Each refined issue uses this format. Separate blocks with ---.
### #N — Title
**Labels:** `label1` `label2`
**Context:** Raw description or user report.
**Refined:** One-line actionable scope or decision.
**My comments:** _(add notes here)_
| Label | Use for |
|---|---|
bug | Something broken or incorrect behavior |
documentation | Docs, README, FAQ, browser support |
enhancement | New feature or improvement |
good first issue | Clear, scoped tasks for contributors |
question | Open questions, naming, investigation |
UI/UX | User-facing behavior, flows, layout |
Brainstorm | Ideas, naming, long-running discussion |
infrastructure | CI/CD, release, monitoring, tooling |
Suggest only these labels; use space-separated list in the block.
*(add notes here)* if no note.