Reconciles project status tracking documents against the actual codebase and git history to fix stale or inconsistent records. Verifies claimed statuses via filesystem checks, git log inspection, and downstream artifact audits. Use when planning a sprint, auditing project progress, fixing summary-detail count drift, or validating that status documents reflect merged PRs and completed work.
89
86%
Does it follow best practices?
Impact
93%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Summary-detail count drift
Filesystem verification
100%
100%
Status corrected for filesystem findings
100%
100%
Detail row counts accurate
100%
100%
Summary table corrected
100%
100%
Estimation table updated
100%
100%
Discrepancies documented
100%
100%
Consistent total counts
100%
100%
Git log consulted
0%
0%
No instruction leakage
100%
100%
Output file names correct
100%
100%
Git history vs status drift
Git log consulted
100%
100%
Merged PRs identified
100%
100%
Filesystem verification
100%
100%
Status entries corrected
100%
100%
Summary count updated
100%
100%
Not Started count corrected
100%
100%
PR references added
100%
100%
Component-level audit trail
100%
100%
DropDownList handled
100%
100%
Downstream artifact completeness
Test file check
100%
100%
Docs check
100%
100%
Nav entry check
100%
100%
RadioButton downgraded
100%
100%
RadioButton missing nav noted
100%
100%
Section header count corrected
100%
100%
Summary table corrected
50%
100%
All three counts consistent
0%
0%
Confirmed-complete components unchanged
100%
100%
1bd9b17
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.