drift-check
FeaturedPre-PR advisory check for deviations from the project spec. Read-only analysis.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- joshukraine
- Repository
- joshukraine/dotfiles
- Created
- 12 years ago
- Last Updated
- 4 weeks ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
pre-pr-check
Pre-flight a contribution to the GuideForge repo before opening a PR — verify every CONTRIBUTING ground rule and PR-checklist item is respected, and that the repo is internally consistent (skill frontmatter valid, README/EXPLAINER skill list in sync, CHANGELOG updated, version stamps aligned, no dead links). Read-only: it reports PASS/FAIL with a checklist, it does not fix. Use right before you `git push` / open a PR against GuideForge. Invoke with no argument to check the current branch's diff, e.g. "/pre-pr-check", or name a base branch, e.g. "/pre-pr-check main".
context-check
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.