genshijin-review

Compresses pull request feedback into line-referenced comments with severity tags.

304|10|Updated Apr 6, 2026

Search Tags:#code review #pull request #GitHub #severity triage #compressed feedback #line-referenced comments

Ready to run

npx skills add https://github.com/InterfaceX-co-jp/genshijin --skill genshijin-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: genshijin-review
Source: https://github.com/InterfaceX-co-jp/genshijin/tree/main/skills/genshijin-review
Command: npx skills add https://github.com/InterfaceX-co-jp/genshijin --skill genshijin-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRレビューで発生する冗長なコメントや前置きによって、重要な指摘が埋もれたり、行動につながりにくい問題を解消します。

Core Features & Use Cases

超圧縮・1行1指摘：位置・問題・修正を1行にまとめて、差分を読んだ直後に判断できる形にします。
重大度で即優先度付け：🔴バグ / 🟡リスク / 🔵nit / ❓質問でコメントの重さを明確化します。
PR貼付可能なフォーマット：L<line>: ...（必要なら <file>:L<line>: ...）で、複数ファイルでも追跡しやすくします。

Quick Start

プルリクエストの差分を貼った状態で「このPRを/genshijin-reviewのルールでレビューして、1行1指摘の形式で出して」と依頼してください。

Frequently Asked Questions about genshijin-review

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

FAQPage Schema

How do I compress pull request review feedback into actionable line-referenced comments?▼

To compress pull request review feedback, the Skill outputs strict L<line>: <issue>.<fix> format comments, combining location, problem, and fix into a single line for immediate action.

What is the best way to triage code review severity for bugs and risks in GitHub?▼

Triage code review severity using strict tagging: 🔴 for bugs, 🟡 for risks, 🔵 for style nits, and ❓ for clarification questions, ensuring priority signals are immediately visible.

Can I review multiple files in a single pull request and still get tracked comments?▼

Yes, you can review multiple files in a pull request. The Skill produces comments using the <file>:L<line>: format when needed, ensuring feedback remains traceable across different files.

How do I format code review comments so developers can act on them instantly?▼

Format code review comments as L<line>: <issue>. <fix> to eliminate redundant preamble. This strict one-line-per-issue format ensures developers read the diff and decide on actions instantly.

Does this code review approach remove unnecessary preamble from pull request comments?▼

Yes, the approach applies strict deletion rules to remove verbose preambles and filler from pull request comments, ensuring only priority signals and actionable fixes remain visible.