vault-sweep

Cross-references Blueprint vault metadata with git history to audit artifact and document statuses.

1|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/luan/agents --skill vault-sweep-luan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-sweep
Source: https://github.com/luan/agents/tree/main/skills/vault-sweep
Command: npx skills add https://github.com/luan/agents --skill vault-sweep-luan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vaults of research, plans, and reference docs drift out of sync as code ships and paradigms change, leaving stale documentation and unused artifacts that slow future development.

Core Features & Use Cases

  • Cross-references the blueprints vault against project reality to determine what features are truly merged, in progress, future-only, or unknown.
  • Audits documentation freshness with deterministic staleness scoring plus qualitative review to decide whether docs should be kept, updated, or archived.
  • Runs gap analysis to propose new reference docs for stable, under-documented systems, improving discoverability for developers.

Quick Start

Ask the AI to run vault-sweep for your repo and produce a structured archive and documentation plan without executing changes by default.

Frequently Asked Questions about vault-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify stale documentation in a blueprints vault?

You can identify stale documentation by cross-referencing vault metadata with git history and codebase verification to compute doc staleness scores and flag consumed artifacts for archival.

What is the best way to audit project hygiene for unused research artifacts?

Auditing project hygiene involves inventorying artifacts via vlt list --json, classifying topics by shipped status, and applying churn-based gap analysis to detect missing reference docs and unused artifacts.

How do I generate a maintenance plan for documentation drift without executing changes?

You can generate a non-executing, approval-gated maintenance plan by running vault-sweep to inventory vault metadata and compute staleness, ensuring you review proposed archival actions before any changes occur.

Can I detect missing reference docs for stable systems using git history?

Yes, you can detect missing reference docs by running churn-based gap analysis via ct repo churn to identify stable, under-documented systems and propose new documentation entries for better discoverability.

Does vault maintenance require checking git history for merged features?

Vault maintenance requires checking git history via ct repo check-refs to determine what features are truly merged, in progress, future-only, or unknown, ensuring documentation accurately reflects project reality.

Why does documentation drift occur in research and plans repositories?

Documentation drift occurs because vaults of research, plans, and reference docs fall out of sync as code ships and paradigms change, leaving stale documentation and consumed artifacts that slow future development.