feat(github): PR action-item context rule#162
Merged
Conversation
Upstreamed from accumulated instance experience into the github inbound-scan (assembles into SKILL only, requires: github): When a PR becomes an action item, the line must state what the PR does, which project it serves, and what's blocked downstream — never just the title and merge status. Captures the change in plain English, the project/area resolved against the KB, who's waiting / what ships on merge, and how long it's waited. A bare title + status is not enough to act on. Generic rule; originating example dropped. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md
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.
Part of the de-personalized Patterns batch — upstreaming accumulated instance rules into the engine phases (Phase-1 work for the connector-based migration, #156). Follows the method from #157.
What
One rule added to
phases/connectors/github.mdinbound-scan (assembles into SKILL only — connector phase,requires: github,mode: [consolidation, briefing]):Complements the existing three-bucket review-request classification right above it (which decides whether a PR is a review item); this rule governs how a PR-derived item is written once it is one.
Verification
_assemble(cfg, kind): lands in SKILL only, not DREAMING/RESEARCH (mode: [consolidation, briefing]).🤖 Generated with Claude Code