Claude Code Skill

deepscan

A project audit skill that creates clear handoff documentation before context compaction or session resumption.

# The Problem

Claude Code sessions have limited context windows. When you compact or start a new session, you lose the thread of where things stand. What was finished? What's half-done? What was the user trying to achieve? You end up re-exploring the same codebase, missing context, and sometimes duplicating or undoing previous work.

Even within a single session, it's easy to lose track of a project's overall state as you bounce between files, fix bugs, and add features.

# What deepscan Does

deepscan is a Claude Code skill that performs a structured five-phase audit of your project. Think of it like a senior engineer doing an end-of-sprint review: walking the repo, checking what shipped, what's stale, and writing up a clear handoff document.

The output is a STATUS.md file and a conversational recap that makes it trivial to resume work — whether after a compact, in a new session, or by a different person picking up the project.

# The Five Phases

Phase 1 — Understand Intent

Read CLAUDE.md, README, package manifests, git log, and conversation history

Synthesize what the project is supposed to be and what the high-level goals are.

Phase 2 — Audit the Repository

Scan for stale docs, unused files, dead code, and inconsistencies

Systematic check with file paths: outdated README sections, duplicate files, commented-out blocks, naming mismatches.

Phase 3 — Assess Progress

Categorize every feature and goal by status

Complete, In Progress, Pending (Claude), Pending (Human), or Unclear. With specific reasons for each.

Phase 4 — Generate STATUS.md

Write a structured handoff document in the project root

Overview, progress table, what's left, cleanup recommendations, and priorities for next session.

Phase 5 — Present and Discuss

Conversational recap with confirmation before any changes

Summarize findings, ask before deleting anything, offer to update stale documentation.

# Example Output

STATUS.md

# Project Status — my-app
> Last reviewed: 2026-02-24
> Reviewed by: Claude (deep scan)

## Progress Summary
| Area              | Status | Notes              |
|-------------------|--------|--------------------|
| Auth system       | ✅     | JWT + refresh flow |
| API endpoints     | 🔧     | 8/12 done          |
| Dashboard UI      | ⏳     | Claude can do      |
| Payment webhooks  | 👤     | Needs Stripe keys  |
| Test coverage     | ❓     | No tests yet       |

## Cleanup Recommendations
### Safe to Delete
- src/old-auth.ts — replaced by src/auth/
- .babelrc — project uses SWC now

# Trigger Phrases

Just say any of these in a Claude Code session:

/deepscan
"review the project"
"what's the state of things"
"recap where we are"
"status check"
"what's left to do"
"audit the repo"
"pre-compact review"

# Install

# Clone the repo
git clone https://github.com/qsimeon/deepscan.git

# Copy to your Claude skills directory
cp -r deepscan ~/.claude/skills/deepscan

# Or symlink it
ln -s $(pwd)/deepscan ~/.claude/skills/deepscan

Then invoke it from any Claude Code session with /deepscan.

Also check out session-merge — a companion skill for merging split Claude Code sessions.