pr-comment-plan SKILL.md skillA
pr-comment-plan from sorafujitani/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sorafujitani/skills/pr-comment-plan@git:20260902.d9838bbPins git:20260902.d9838bb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sorafujitani/skills
- Path
pr-comment-plan/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260902.d9838bb, committed Sep 2, 2026
- First version recorded
- May 8, 2026
- Size
- 3,715 bytes
- Repository stars
- 8
- License
- MIT
明示的に `pr-comment-plan` を呼び出した場合のみ使用する。 GitHub PRのレビューコメント分析と改善計画の策定。 現在のブランチに関連するPRの未解決コメントを取得・分析し、 重要度分類(Critical/Important/Minor)と体系的な改善実行計画を生成する。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# PR Comment Analysis & Improvement Planning
あなたはGitHub PRのレビューコメント分析と改善計画の専門家です。現在のブランチに関連するPRの未解決コメントを取得・分析し、体系的な改善計画を策定します。
## 実行手順
1. **PR特定**
- 現在のブランチ名を確認: `git branch --show-current`
- 関連するPR番号を特定: `gh pr list --head [branch-name] --json number,url --jq '.[0]'`
2. **PRコンテキスト取得**
- `gh pr view --json` と `gh api` で PR 情報(body, comments, reviews, files)を一括取得する
- プロンプト例: `"{owner}/{repo}#{PR番号} のPR情報を取得して"`
- 返却される構造化コンテキスト(`=== GITHUB_CONTEXT: PR ===` ブロック)からメタデータ・BODY・REVIEW_STATUS・FILES・COMMENTSを利用する
- インラインレビューコメント(ファイル・行単位)が必要な場合は追加で取得: `gh api repos/{owner}/{repo}/pulls/{PR番号}/comments --jq '.[] | {path, line, body, user: .user.login, created_at}'`
3. **コメント内容の分析**
- **重要度分類**:
- 🔴 Critical: バグ、セキュリティ、パフォーマンス問題
- 🟡 Important: 設計改善、コード品質
- 🟢 Minor: スタイル、命名、ドキュメント
- **カテゴリ分類**:
- Logic/Bug: ロジックエラーやバグ
- Performance: パフォーマンス関連
- Security: セキュリティ懸念
- Design: 設計・アーキテクチャ
- Code Quality: コード品質・可読性
- Testing: テスト関連
- Documentation: ドキュメント・コメント
4. **改善計画の策定**
- コメントの優先順位付け
- 依存関係の特定
- 実装順序の決定
- 各改善の影響範囲評価
5. **実行計画の作成**
- 具体的な修正手順
- 各修正のコミット計画
- テスト・検証方法
## 出力形式
### 📊 PR情報
…Read the whole file at its exact version.
How to install
mdr add sorafujitani/skills/pr-comment-plan@sha256:68974bac4ff0f34bThe line at the top of this page pins the label git:20260902.d9838bb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3zy6w4v7ppozujj3)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 8, 2026 and Sep 2, 2026, about one every 117 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260902.d9838bb latest | 2026-09-02 | d9838bb | 3,715 B | A | view · diff |
| git:20260508.f63bdbf | 2026-05-08 | f63bdbf | 4,012 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3715 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sorafujitani/skills · 8 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3zy6w4v7ppozujj3 GET https://markdownregistry.com/api/v1/resolve?ref=sorafujitani/skills/pr-comment-plan GET https://markdownregistry.com/api/v1/blob/68974bac4ff0f34b2763d5cacec01769306bb6b5192b327fc26ac5f5b68974b9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.