Evaluate pull requests against approved implementation plans with CI checks.
npx skills add https://github.com/rjskene/pipeline --skill evaluate-issue-pr
Please help me install this Agent Skill. Skill: evaluate-issue-pr Source: https://github.com/rjskene/pipeline/tree/main/skills/evaluate-issue-pr Command: npx skills add https://github.com/rjskene/pipeline --skill evaluate-issue-pr
It independently checks whether a submitted pull request correctly implements an already-approved implementation plan, and produces a clear approval or flagged verdict to protect merges.
Use /pipeline:evaluate-issue-pr <issue_number> inside the feature worktree to review the PR against its trusted implementation plan and post an evaluation verdict.
High-intent search queries and answers about installing and using this skill.
To verify a pull request matches an approved implementation plan, you can use an automated evaluation gate that retrieves the trusted plan, checks the diff against required files and categories, and runs typecheck and tests to produce a clear approval verdict.
Yes, you can prevent merging when CI checks fail by using a merge gate that detects failed or cancelled CI statuses, blocks approval for red PRs, and optionally retries with a fix when permitted by budget.
You can check the diff automatically for security risks and missing error handling by running a quality review that inspects PR changes to flag leftover debug code, injection/XSS risks, and insufficient test coverage.
Yes, the PR review process supports visual proof verification by invoking a visual-proof skill to adjudicate browser evidence, checking screenshot claims and flagging unsatisfied requirements for human review.
To run typecheck and merge gate verification on GitHub PRs, you need command-line dependencies including gh, jq, timeout, bash, realpath, npm, and npx tsc installed in your execution environment.
You should not use an automated auto-merge gate when you need manual control over the integration process, or when your workflow does not rely on a pre-approved implementation plan to dictate the required file changes and test coverage.
rjskeneEvaluate GitHub issue implementation plans against repository code and issue requirements.
LeonardoTan19Guide merge, PR, or discard decisions for completed development branches.
vTRKAEnforce scoped safety controls and generate browser-agent-safety-report artifacts before browser automation.
AlabamaMikeRun verification commands and confirm fresh outputs before declaring completion.
