メニュー
Review code quality, patterns, and bugs. Use when asked to "review the code", "check code quality", "look for bugs", "review implementation", or when evaluating code correctness, security, and maintainability independent of the diff or PR context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill to understand the claude marketplaces in the nsheaps github org: the plugin marketplace build, release, and propagation pipeline. Recall this skill when working on CI/CD workflows, mise tasks, plugin versioning, marketplace updates, or when asked how plugins get from source code to a user's Claude Code installation. Also recall when debugging version bumps, marketplace.json drift, or plugin cache issues.
Use this skill when the user asks about GitHub operations, pull requests, issues, releases, actions, gists, repos, or any task involving the GitHub CLI (gh). Also use when needing to interact with GitHub APIs, check CI status, review PRs, manage labels, create releases, or automate GitHub workflows from the command line.
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
Manage GitHub App installation tokens in Claude Code sessions. Use when tokens expire, auth errors occur in long-running sessions, or when setting up GitHub App credentials for agent teams. <example>my github token expired</example> <example>refresh the github app token</example> <example>check token status</example> <example>set up github app authentication for this session</example>
Manages spec files for requirements capture and validation
| name | review-code |
| description | Review code quality, patterns, and bugs. Use when asked to "review the code", "check code quality", "look for bugs", "review implementation", or when evaluating code correctness, security, and maintainability independent of the diff or PR context. |
| argument-hint | [file path, directory, or PR number to scope the review] |
Evaluate the code itself for quality, correctness, and adherence to best practices.
| Dimension | Check for |
|---|---|
| Correctness | Does the code do what it claims? Edge cases handled? |
| Security | Injection, auth issues, secrets exposure, unsafe APIs |
| Performance | Obvious bottlenecks, N+1 queries, unnecessary copying |
| Maintainability | Readable? Can someone else modify it in 6 months? |
| Simplicity | Is there unnecessary complexity? Could it be simpler? |
| Pattern match | Does it follow existing codebase conventions? |
| Error handling | Are errors caught, logged, and surfaced appropriately? |
