sanity-check

Reviews repository contributions for necessity, duplication, contracts, and scope with evidence-backed verdicts.

294|16|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/osolmaz/pi-workflows --skill sanity-check-osolmaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sanity-check
Source: https://github.com/osolmaz/pi-workflows/tree/main/skills/sanity-check
Command: npx skills add https://github.com/osolmaz/pi-workflows --skill sanity-check-osolmaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers whether a code contribution is actually necessary and well-scoped before merging, catching duplicated logic, unjustified contracts, and disproportionate changes without modifying any files. ## Core Features & Use Cases - Read-only contribution review: Collects committed diffs, working-tree changes, untracked files, and pull-request metadata, then reviews necessity, duplication, contracts, and scope with tests. - Verified verdicts: Runs isolated reviews per area plus a separate verification pass, returning a keep, simplify, refactor, drop, or needs-evidence verdict backed by exact file and symbol evidence. - Serial or parallel modes: Serial mode reviews all four areas in one isolated session; parallel mode runs one review per area with concurrency four. - Use Case: Before merging a pull request, ask for a sanity check against origin/main to confirm the change is necessary, non-duplicative, and proportionately tested. ## Quick Start Ask the agent to run a sanity check on the current repository's changes against origin/main and report whether the contribution should be kept, simplified, refactored, or dropped.

Frequently Asked Questions about sanity-check

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

FAQPage Schema
How do I check if a code contribution is necessary before merging?▼

Run the sanity-check workflow against a base reference such as origin/main. It reviews necessity, duplication, contracts, and scope with tests, then returns a verified keep, simplify, refactor, drop, or needs-evidence verdict with file-level evidence.

How to review a pull request for duplicated code and scope creep?▼

Start the sanity-check workflow in serial mode, which reviews all four areas in one isolated session. It collects the committed diff, working-tree changes, untracked files, and pull-request metadata to detect duplication and disproportionate scope.

Does the sanity check modify files or post comments?▼

No, the workflow is strictly read-only. It collects evidence, runs isolated reviews, verifies claims, and reports findings as assistant messages without editing files, posting comments, or fixing findings.

What is the difference between serial and parallel review modes?▼

Serial mode reviews all four areas in one isolated session and is the default. Parallel mode runs one isolated review per area with concurrency four, and both modes run a separate verification review of the findings.

Can I run the sanity check outside the Pi agent?▼

Yes, the skill defines a manual fallback: collect the committed and working-tree diffs plus pull-request context, review the four areas with exact evidence, verify findings, and return a verdict while staying read-only.