Run verification checks on changed code, tables, and manuscript sections.
npx skills add https://github.com/naj2r/claude-econ-paper-template --skill verify-naj2r
Please help me install this Agent Skill. Skill: verify Source: https://github.com/naj2r/claude-econ-paper-template/tree/main/.claude/skills/verify Command: npx skills add https://github.com/naj2r/claude-econ-paper-template --skill verify-naj2r
This Skill enforces mandatory verification after any code, table, bibliography, or manuscript section change to prevent silently incorrect outputs, broken cross-references, unresolved citations, and mismatched regression or table results.
Run verification on the changed file or section and produce a verification report indicating PASS or FAIL.
High-intent search queries and answers about installing and using this skill.
To verify Stata do-file outputs and Quarto rendering, you must run post-change verification checks that inspect logs for errors, execute scripts end-to-end, and render the Quarto book to detect mismatched outputs and broken cross-references.
Validating citation keys in a .bib file involves running grep-based citation validation to check for unresolved references and ensure that bibliography modifications align with manuscript cross-references before producing a PASS/FAIL report.
Checking LaTeX tables for structural errors requires verifying table structure and labels against generated outputs, performing diff comparisons with prior outputs, and confirming regression consistency to prevent silently incorrect results.
Yes, you can run post-change verification on R scripts and Overleaf sections simultaneously by applying the prescribed verification matrix, which inspects logs, runs scripts end-to-end, and validates cross-references across all modified manuscript sections.
Quarto book rendering fails after updating a data processing script due to mismatched outputs, broken cross-references, or unresolved citations that post-change verification detects through log inspection and end-to-end script execution.
No, you do not need to manually diff generated tables after running a Stata do-file, because the verification workflow automatically performs diff comparisons of outputs against prior results and produces a structured PASS/FAIL verification report.
maxwell2732Render Quarto Stata reports after verifying engine, freshness, citations, and numerical claims.
krzemienskiVerify gate checkpoint evidence and cite exact outputs for pass/fail status.
naj2rInsert LaTeX \input commands linking generated table files into Overleaf sections.
0xmariowuReview code changes, test results, and project plans before deployment.
