governance-pr-summary

Inject computed Module Grade results into pull request descriptions.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill governance-pr-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-pr-summary
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/governance-pr-summary
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill governance-pr-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents module work from turning into slow, manual governance by ensuring every PR that touches Modules/<X>/ carries an up-to-date Module Grade summary where reviewers can see it immediately.

Core Features & Use Cases

  • Automated module detection from git diff: identifies affected Modules/<X>/ paths and infers which module bucket applies.
  • Grade computation with safe fallback: prefers php artisan module:grade-v4 --json and falls back to v3 when v4/scoped scorecards aren’t available.
  • PR description injection: inserts the ## Module Grade v4 (Scoped Scorecards) section (or the v3 fallback section) into the PR body before gh pr create, using real computed results and bucket targets.

Quick Start

Before creating your PR with gh pr create, ask the AI to run governance-pr-summary so it auto-detects affected modules from your diff and injects the computed Module Grade section into the PR description.

Frequently Asked Questions about governance-pr-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically inject a module grade summary into GitHub pull request descriptions?

Automated module grade injection works by detecting affected Modules/<X>/ paths from your git diff, computing the grade via Laravel artisan, and inserting the markdown summary into the PR body before creation.

How does git diff module detection work for PR governance?

Module detection analyzes your git diff to identify affected Modules/<X>/ paths and infers the applicable module bucket, ensuring the correct scoped scorecards are computed for PR governance.

What happens if Laravel artisan module grade v4 is not available?

If Laravel artisan module:grade-v4 is unavailable, the Skill safely falls back to the v3 command, computing module grades and inserting the corresponding v3 markdown section into the PR description.

Can I use this with standard gh pr create workflows?

Yes, this integrates with standard gh pr create workflows; run the governance-pr-summary process beforehand to automatically compose and insert the correct markdown section into the PR body.

What is a scoped scorecard in PR module grading?

A scoped scorecard in PR module grading represents computed results from running module grade v4 with bucket scoping, evaluating module health and inserting the summary into the PR description for reviewer alignment.