Context Engineering: Verify Documentation
Check if documentation line numbers still match the actual code.
Purpose
After code changes, line numbers in documentation may drift. This skill:
- •Finds all
file:linereferences in.claude/documentation - •Verifies the referenced lines exist and match described content
- •Reports accuracy and suggests fixes
Process
- •
Scan Documentation
- •Find all patterns like
file.py:123or[file.py:123] - •Extract file path and line number
- •Find all patterns like
- •
Verify References
- •Check if file exists
- •Check if line number is within file bounds
- •Sample content to verify it matches description
- •
Calculate Accuracy
- •Total references found
- •Valid references
- •Accuracy percentage
- •
Generate Report
codeDocumentation Accuracy Report ============================= Total References: 156 Valid: 142 Invalid: 14 Accuracy: 91% Invalid References: - context/workflows/auth.md:45 → src/auth.py:230 (line moved to 245) - context/workflows/api.md:12 → src/api.py:100 (file renamed)
Usage
Check specific file:
code
/context-eng:verify-docs path/to/changed/file.py
Check all documentation:
code
/context-eng:verify-docs
Auto-fix (update line numbers):
code
/context-eng:verify-docs --fix
Target Accuracy
| Level | Accuracy | Action |
|---|---|---|
| Excellent | ≥80% | No action needed |
| Good | 60-80% | Update when convenient |
| Warning | 40-60% | Update soon |
| Critical | <40% | Update immediately |
When to Run
- •After refactoring
- •After adding/removing significant code
- •Before creating a PR
- •Weekly maintenance