Full Project Integrity Check

VerifiedSafe

Run a two-phase project integrity check covering pipeline scripts, data files, directories, and manuscript references.

Sby Skills Guide Bot
Data & AIIntermediate
107/29/2026
Claude CodeCursorWindsurfCopilotCodex
#reproducibility#pipeline-check#manuscript-audit#file-consistency

Recommended for

Our review

Executes a comprehensive integrity check for a reproducible research project, including pipeline consistency and a LaTeX manuscript audit.

Strengths

  • Automatically verifies that all listed scripts and data files exist and are correctly placed.
  • Audits cross-references between the manuscript and output files.
  • Detects orphan or undocumented files in the project.
  • Does not modify anything without explicit user approval.

Limitations

  • Requires the project to follow a standard structure with README and manuscript.tex.
  • Does not check script content or data validity.
  • Does not automatically fix identified issues.
When to use it

Use this skill before submitting a paper or sharing a project to ensure all parts are consistent and documented.

When not to use it

Do not use it if the project lacks a structured README or LaTeX manuscript, or if you want automatic issue correction.

Security analysis

Safe
Quality score85/100

The skill provides a high-level checklist for manually verifying project integrity. It does not instruct on any executable commands, data exfiltration, or destructive actions. No tools are declared or invoked.

No concerns found

Examples

Full integrity check
Run a full project integrity check including pipeline integrity and manuscript audit.
Check pipeline only
Check pipeline integrity: verify that all scripts and data files listed in the README exist, that no files are in wrong directories, and that output directories exist.
Audit manuscript references
Audit the manuscript: verify that every \includegraphics and \input in manuscript.tex resolves to an existing file, check that all entries in the README table/figure map have corresponding outputs, and list any orphan outputs or undocumented references.

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