issue-review

Review worktree edits against GitHub Issue requirements and code quality.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/chiyonn/dotfiles --skill issue-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-review
Source: https://github.com/chiyonn/dotfiles/tree/main/dot_claude/skills/issue-review
Command: npx skills add https://github.com/chiyonn/dotfiles --skill issue-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

このスキルは、Issueに紐づく worktree の編集内容を厳しくレビューすることで、要件との整合性とコード品質を担保します。Issue番号を指定するだけで、対応範囲の適合性、テストの網羅性、セキュリティ観点を自動的に検証します。

Core Features & Use Cases

  • Issue要件との整合性チェック: 指定されたIssue番号に対して、目的・機能・制約が反映されているかを検証します。
  • コード品質・テスト・セキュリティの観点チェック: コーディング標準、テストの可用性、潜在的なセキュリティ脆弱性を検出します。
  • レビュー実行のトリガーと出力: 「Issue 4をレビューして」や「#7のレビュー」で起動し、結果を要約して返します。

Quick Start

Issue番号を指定してレビューを開始します。例として「Issue 4をレビューして」や「#7のレビュー」で起動します。実行コマンドの例は下記を参照してください。

  • Trigger phrases: Issue 4をレビューして or #7のレビューで起動
  • Example command: issue-review 4

Frequently Asked Questions about issue-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes tied to a GitHub Issue automatically?

You can review GitHub Issue worktrees by specifying the issue number, such as 'Issue 4' or '#7', which triggers an automated validation of requirements, code quality, tests, and security.

What does an issue-worktree review check for in my codebase?

An issue-worktree review checks for alignment with issue requirements, coding standards, test coverage, and potential security vulnerabilities to ensure traceable and rigorous quality outcomes.

Can I use gh CLI to fetch GitHub Issue data for worktree reviews?

Yes, you can use git and gh CLI to fetch GitHub Issue data and analyze worktree edits, ensuring validation against issue requirements and security standards.

Do I need to install any dependencies to run issue-based code reviews?

No additional dependencies are required, but you need git and gh CLI available in your environment to fetch issue data and analyze worktree edits.

What is the best way to ensure my worktree edits meet issue requirements?

The best way is to run an automated review that enforces checks against the issue's purpose, functionality, and constraints, returning a traceable summary of compliance and quality.

Why are my worktree edits failing the issue requirement checks?

Worktree edits fail issue requirement checks when the code does not reflect the issue's purpose, functionality, or constraints, or when potential security vulnerabilities and missing tests are detected.