Papi Verify
- 1 installs
- 35 repo stars
- Updated August 1, 2026
- hummat/paperpipe
Verify code against a paper by mapping paper symbols to code variables, flagging mismatches like wrong sign/scale or shape bugs, and proposing minimal fixes and tests.
About
Checks whether a code implementation matches the equations and algorithms in a paper, building a symbol-mapping table and a mismatch list. A developer uses it to catch sign, scale, normalization, and shape errors when implementing from literature.
- Symbol-mapping table with shapes and units
- Mismatch/risk list plus a minimal fix plan and suggested tests
Papi Verify by the numbers
- 1 all-time installs (skills.sh)
- Ranked #984 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hummat/paperpipe --skill papi-verifyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 35 |
| Last updated | August 1, 2026 |
| Repository | hummat/paperpipe ↗ |
What it does
Verify code against a paper by mapping paper symbols to code variables, flagging mismatches like wrong sign/scale or shape bugs, and proposing minimal fixes and tests.
Files
Verify Code Against Paper
You are given:
- Code (or a code excerpt), plus paper excerpts (paste
papi show ... --level ...output above, or reference exported files).
Project context (optional): $ARGUMENTS
Rules
- Prefer equations/LaTeX over summaries when there's a conflict.
- If a claim is not supported by provided excerpts, say: "Not supported by provided excerpts."
- For supported claims, include a short quote snippet (<= 15 words) and cite as:
(paper: <name>, arXiv: <id if present>, source: summary|equations|tex|notes, ref: section/eq/table/figure if present)
Output
1) Symbol mapping table: paper symbol/definition → code variable/tensor (include shapes/units if stated) 2) Mismatches / risks (bulleted): missing terms, wrong sign/scale/normalization, shape bugs, hidden assumptions 3) Fix plan: minimal code changes (or patch sketch) + suggested asserts/tests to lock correctness
End with: Cited papers: <comma-separated paper names and/or arXiv IDs>
For general CLI commands, see /papi.
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264k