skills/plan-archive/SKILL.md
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
npx skillsauth add arndvs/ctrlshft plan-archiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Archives ~/.claude/plans/*.md files by matching them to merged PRs via
file-overlap analysis, then moves them into organized directories with
metadata linking back to the PR, Linear tickets, and commits.
List all active plans with last-modified dates. Good for seeing what's accumulated.
python3 skills/plan-archive/plan-archive.py --mode=audit
Match plans to a specific merged PR and archive the bundle:
# Dry-run — see what would move
python3 skills/plan-archive/plan-archive.py --mode=archive-pr --pr=42
# Execute — actually move files
python3 skills/plan-archive/plan-archive.py --mode=archive-pr --pr=42 --execute
Scan all merged PRs within a window and archive matching plans:
# Dry-run — see what would be archived
python3 skills/plan-archive/plan-archive.py --mode=backfill --since=30d
# Execute
python3 skills/plan-archive/plan-archive.py --mode=backfill --since=2w --execute
Archived plans go to ~/.claude/plans/archive/by-pr/PR-<num>-<branch-slug>/
with a _meta.yaml containing:
| Flag | Description |
|------|-------------|
| --mode | audit, archive-pr, or backfill (required) |
| --pr | PR number (required for archive-pr) |
| --since | Time window for backfill: 30d, 2w, 12h (default: 30d) |
| --execute | Actually move files (default: dry-run) |
| --repo | Override GitHub repo (default: cwd's repo) |
| --plans-dir | Override plans directory (default: ~/.claude/plans) |
| --limit | Max PRs to fetch for backfill (default: 200) |
gh pr diff --name-only## Files section for declared file pathsdevelopment
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
development
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
testing
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
testing
Pre-flight checklist that runs quality gates before ending a coding session.