Skip to content

Assess knowledge uplift in the code-review skill and PR Review board - #5046

Merged
aaronpowell merged 1 commit into
mainfrom
aaronpowell-pr-review-knowledge-uplift
Oct 13, 2026
Merged

aaronpowell merged 1 commit into
mainfrom
aaronpowell-pr-review-knowledge-uplift

Conversation

@aaronpowell

Copy link
Copy Markdown
Contributor

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the main branch for this pull request.

Description

AI reviews can approve well-formatted resources without establishing whether they improve on what a capable model already does. This adds an explicit knowledge-uplift test to the repository's code-review skill so the criterion applies beyond the PR Review canvas.

The skill compares behavior with and without the resource, distinguishes specific knowledge and workflow constraints from generic advice, and requires cited evidence for a high, partial, or none classification. The board references that canonical test rather than duplicating it, records the classification first in differentiation, and maps absent or partial uplift to non-approval recommendations.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • New canvas extension.
  • Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
  • Other (please specify):

Additional Notes

This strengthens review policy: no uplift must not receive approval, and partial uplift asks authors to remove generic sections and expand the useful core. Maintainer review of the policy change is needed.

Validation:

  • npm start: passed; generated README and marketplace output remain unchanged.
  • bash eng/fix-line-endings.sh: passed.
  • node --experimental-vm-modules --test eng/open-pr-board.test.mjs eng/board-bulk-actions.test.mjs eng/board-state-storage.test.mjs: passed, 49 tests.
  • git diff --check: passed.

Live Copilot review calibration was not run. Paid-service guidance and new-resource checklist items are not applicable.


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Centralize the knowledge-uplift test in the code-review skill and require evidence-backed classifications in the PR Review board.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 9082818f-c7db-42c7-add6-c337afb05fdb
Copilot AI balanced review requested due to automatic review settings October 13, 2026 04:58
@aaronpowell
aaronpowell requested a review from a team as a code owner October 13, 2026 04:58
@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier
  • .github/extensions/open-pr-board/lib/review-prompt.mjs is a high-risk path (automation, scripts, MCP config, hooks, or review policy)
  • .github/extensions/open-pr-board/review-guidance.md is a high-risk path (automation, scripts, MCP config, hooks, or review policy)
  • .github/skills/code-review/SKILL.md is a high-risk path (automation, scripts, MCP config, hooks, or review policy)

Automated checks

Check Status Details
Line endings ✅ Passed Passed · logs
Spelling ✅ Passed Passed · logs
Contributor reputation ✅ Passed Passed · logs
Duplicate resource scan ⏳ Pending (advisory, non-blocking) Running · logs
PR quality signal ⏳ Pending (advisory, non-blocking) Running · logs

Review

  • Approvals: 0/1
  • Assigned reviewer: not assigned yet — comment /request-review to ask for one
  • Review target date: not set
  • Still needed: 1 more approval(s); an approval from a maintainer with admin or maintain permission
  • The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command Who What it does
/rerun-checks PR author, maintainers Re-runs failed or incomplete checks and re-evaluates this gate
/request-review PR author, maintainers Asks the review rotation to assign a reviewer (adds needs-reviewer)

Updated for 17ffd2e · gate run · This comment is maintained automatically — see submission gate docs.

@github-actions

Copy link
Copy Markdown
Contributor

🟡 Contributor Reputation Check: MEDIUM risk

Check Risk
Profile MEDIUM
Credential audit NONE

Maintainers: please review this contributor before merging.
See the workflow run for full details.
Automated check powered by AGT.

@github-actions github-actions Bot added needs-review:MEDIUM Contributor reputation check flagged MEDIUM risk ready-for-review Submission passed intake validation and is ready for maintainer review and removed awaiting-automation labels Oct 13, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The partial-uplift wording still permits approval, and this governance-sensitive policy change requires maintainer review.

2 open findings
What changed in this PR

Adds a canonical knowledge-uplift assessment to repository review policy and integrates it into the Open PR Board.

Changes:

  • Defines high, partial, and none uplift classifications.
  • Adds uplift evidence to board guidance and structured review prompts.
  • Updates the differentiation schema description.

Knowledge uplift: High—the policy introduces repository-specific classification and approval constraints.

File Description
.github/​skills/​code-review/​SKILL.md Defines the canonical uplift test.
.github/​extensions/​open-pr-board/​review-guidance.md Maps uplift results to board recommendations.
.github/​extensions/​open-pr-board/​lib/​review-prompt.mjs Adds uplift requirements to review prompts and schema.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

return [
"Knowledge uplift — apply the \"Knowledge uplift\" test from the code-review skill to every agent, instruction, skill, prompt, hook, or workflow the PR adds or substantially changes. It is the criterion most often under-applied, so do not skip it for well-formatted PRs:",
" - Always start the `differentiation` field with the `high` / `partial` / `none` classification and the quoted lines that justify it, then note any overlap with existing resources.",
" - `none` must not be `approve`: use `needs-insight`, or `close` when it is also a near-duplicate. `partial` is usually `request-changes`; name the generic sections to cut in `suggestedComment`.",
- **Knowledge uplift** — the most common way a well-formatted PR still fails. Apply the
"Knowledge uplift" test from `.github/skills/code-review/SKILL.md` to every content
resource. `none` is never `approve` (use `needs-insight`, or `close` if it is also a
near-duplicate); `partial` is usually `request-changes`.
@aaronpowell
aaronpowell merged commit 8182417 into main Oct 13, 2026
27 of 29 checks passed
@aaronpowell
aaronpowell deleted the aaronpowell-pr-review-knowledge-uplift branch October 13, 2026 05:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk:high needs-review:MEDIUM Contributor reputation check flagged MEDIUM risk ready-for-review Submission passed intake validation and is ready for maintainer review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants