メニュー
Formats GitHub issue suggestions with a short title and informal problem description. Use when proposing GitHub issues for bugs, features, or improvements discovered during work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | issue-format |
| description | Formats GitHub issue suggestions with a short title and informal problem description. Use when proposing GitHub issues for bugs, features, or improvements discovered during work. |
> **GitHub issue:**
> - **Title:** `short issue title here`
> - **Description:** 2-3 sentences describing the problem as if unresolved.
> **GitHub issue:**
> - **Title:** `useReplies returns stale data after reset`
> - **Description:** When calling `reset()` on `useReplies`, subsequent `loadMore` calls return previously cached replies instead of fetching fresh data. This causes the UI to show outdated replies after a user manually refreshes a thread.
Advisory pre-push/pre-PR code quality review for current diffs. Use when asked to review code quality, run a pre-PR or pre-push quality pass, inspect AI-generated changes, check for over-engineering, or before pushing/opening a PR. Reports actionable suggestions only; does not block or edit unless explicitly asked.
Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says "make closed issue", "close issue", or wants to create a tracked, already-resolved GitHub issue for completed work.
Commit current work by reviewing diffs, splitting into logical commits, and writing standardized messages. Use when the user says "commit", "commit this", "commit current work", or asks to create a git commit.
Scan recent changes for AI-generated code slop and remove it. Use when the user says "deslop", "remove slop", "clean up AI code", or asks to remove AI-generated artifacts from the codebase.
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, dead-code removal, or says "refactor pass".
Analyze code for useEffect anti-patterns and refactor to simpler alternatives. Use when the user says "you might not need an effect", "check effects", "useEffect audit", or asks to review useEffect usage.