From 44760a92b04109cd7a0dd05055e7cf93b17ec5d1 Mon Sep 17 00:00:00 2001 From: Jordan Burger Date: Tue, 23 Jun 2026 14:06:46 -0400 Subject: [PATCH] feat(github): PR action-item context rule MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- CHANGELOG.md | 3 +++ phases/connectors/github.md | 11 +++++++++++ 2 files changed, 14 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ee62a93..95c91b0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,9 @@ this project adheres to [Semantic Versioning](https://semver.org/). ## [Unreleased] +### Added +- **GitHub PR action-item context** (`phases/connectors/github.md`) — a rule upstreamed from accumulated instance experience: 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 context to act on. + ## [0.7.2] - 2026-06-22 diff --git a/phases/connectors/github.md b/phases/connectors/github.md index df49894..8eb254f 100644 --- a/phases/connectors/github.md +++ b/phases/connectors/github.md @@ -70,6 +70,17 @@ gh search prs --review-requested @me --state open --json number,title,url,reposi Pull `gh pr view N --repo R --json author,headRefName,reviewRequests,isDraft` to classify. For buckets 2–3, note who requested it, which repo, how long it's waited (prioritize older), and PR size if available. +### PR Action-Item Context + +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. A reader seeing only "Review PR #123 — open" has to open the PR to learn whether it matters; the action item exists to spare them that. For every PR-derived item, capture: + +- **What it does** — the change in one plain-English phrase, not the raw PR title. +- **Which project/area** — resolve the repo/PR against the KB so it links to the right project entity, not just a bare repo name. +- **What's blocked** — who is waiting on it, or what ships once it merges. "Review feedback needing a response" and "approval blocking a release" are different priorities; the downstream context is what distinguishes them. +- **How long it's waited** — staleness drives ordering. + +A bare title + status is not enough context to act on. + ### New Issues Assigned ```bash