Project Integrity Check

VerifiedSafe

Runs a full project integrity check on pipeline and manuscript, ensuring all files, scripts, and references exist and are consistent.

Sby Skills Guide Bot
DevelopmentIntermediate
108/1/2026
Claude CodeCursorWindsurfCopilotCodex
#integrity-check#pipeline-audit#manuscript-validation#reproducibility

Recommended for

Our review

Runs a full project integrity audit in two phases: pipeline verification and manuscript reference checking.

Strengths

  • Checks both code/data pipeline and manuscript outputs
  • Detects orphaned files and missing references
  • Does not modify anything without user approval

Limitations

  • Assumes a specific README structure with pipeline tables and figure/map listings
  • Requires all files to be in expected directories
  • May not cover all project-specific conventions
When to use it

When you need to ensure a reproducible research project is complete and consistent before sharing or submission.

When not to use it

When the project does not follow a README-based structure or you need to fix issues automatically.

Security analysis

Safe
Quality score92/100

Skill performs read-only integrity checks without executing any scripts or making changes; no network access, system modification, or risky tools are employed.

No concerns found

Examples

Full integrity check
Run the project integrity check on this repository and report all findings.
Manuscript audit only
Check the manuscript.tex references and table/figure map for any missing files or undocumented outputs.
Pipeline verification
Verify that all scripts and data files listed in the README pipeline table exist and are in the correct directories.

Run a full project integrity check. Two phases:

Phase 1 — Pipeline integrity: (1) Every script listed in README pipeline table exists. (2) Every input data file listed exists. (3) No scripts or data files sitting in wrong directories. (4) Output directories exist. (5) params.do values match README parameters table.

Phase 2 — Manuscript audit: (1) Every entry in README table/figure map has an existing output file and source script. (2) Every \includegraphics and \input in manuscript.tex resolves to an existing file. (3) Find any output files not referenced in the manuscript (orphans). (4) Find any manuscript references not in the table/figure map (undocumented).

Report all findings. Do not fix anything without user approval.

Related skills