Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Before creating a PR, the skill now groups changed files by concern and stops to suggest splitting if changes span 2+ unrelated areas (e.g. feature + infra). Threshold: ~400 lines or 3+ concerns. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
概要
/git-prスキルが PR を作成する前に、変更の粒度を自動チェックするようにした。背景
PR に複数の無関係な変更（例：機能追加 + インフラ修正）が混在していると、レビュー負荷が高くなる。
実際に今日のセッションで、CI スクリプト追加・vitest 修正・vercel.json 変更が1つの PR に混入する問題が起きたため、スキルレベルで防ぐ仕組みを追加した。
変更内容
.agents/skills/git-pr/SKILL.mdにステップ2として粒度チェックを追加：動作
🤖 Generated with Claude Code