skills.rest
pbs
pbsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

check-last-pr

Analyzes pull requests and recommends whether to merge, revise, or reject them.

272|141|Updated Jun 1, 2012
Search Tags:#automation#compliance#merge#review#pr#code-review
One-click install
npx skills add https://github.com/pbs/pycaption --skill check-last-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-last-pr
Source: https://github.com/pbs/pycaption/tree/main/.claude/skills/check-last-pr
Command: npx skills add https://github.com/pbs/pycaption --skill check-last-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR reviews are time-consuming and error-prone. check-last-pr automates comprehensive PR analysis to guide merge decisions, surfacing compliance gaps, regressions, and coverage gaps.

Core Features & Use Cases

  • Auto-detects SCC, VTT, and/or DFXP flow from changed files to tailor compliance checks.
  • Performs spec-compliance checks for NEW issues introduced by the PR against spec summaries.
  • Conducts full code review for regressions, breaking changes, and test coverage.
  • Provides change analysis that explains what the changes do and how they address the issue.
  • Delivers a clear recommendation: merge / needs work / do not merge.

Quick Start

Run the check-last-pr command on the current branch to generate a comprehensive review.

Frequently Asked Questions about check-last-pr

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

FAQPage Schema
How do I automate code review for safe pull request merges?▼

Automated code review for safe merges analyzes pull requests to detect regressions, verify spec compliance, and evaluate test coverage, delivering an actionable merge recommendation.

What is the best way to check PR compliance before merging code changes?▼

Checking PR compliance before merging auto-detects execution flows from changed files to tailor compliance checks, surfacing gaps and new issues introduced against specification summaries.

How does automated PR analysis detect regressions and breaking changes?▼

Automated PR analysis detects regressions by conducting a full code review of execution flow, documentation, and test changes, identifying breaking changes and coverage gaps.

Can I get an automated merge recommendation for documentation and test changes?▼

Yes, you can get an automated merge recommendation for documentation and test changes by running analysis on the current branch to generate a comprehensive review.

Does automated PR analysis work without external dependencies?▼

Yes, automated PR analysis works without external dependencies, applying compliance checks and code review directly to the changed files in your current branch.

Why should I use automated PR analysis instead of manual code review?▼

Automated PR analysis eliminates the time-consuming and error-prone nature of manual reviews by automatically delivering clear merge, needs work, or do not merge recommendations.

Related Skills

Explore More Software Engineering Skills→
huGgWhuGgW
1

pr-description

Generate a README.md file from a Jupyter notebook's metadata and content.

Community
Advanced
ajsai47ajsai47
11

land-and-deploy

Merge GitHub pull requests and verify production health after deployment.

Community
Advanced
Rune-kitRune-kit
82

sast

Run static analysis tools and normalize findings into unified severity levels.

Official
Advanced
blakeoxblakeox

enforcer

Automate code review and release safety assessments for software development workflows.

Community
Intermediate