project-scout

Survey repository trees to classify document clusters into an adoption taxonomy.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/rjwalters/bucket-brigade --skill project-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-scout
Source: https://github.com/rjwalters/bucket-brigade/tree/main/.anvil/skills/project-scout
Command: npx skills add https://github.com/rjwalters/bucket-brigade --skill project-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of surveying large repositories to identify which documents are ready for adoption into the Anvil documentation system. Without automated discovery, operators must manually inspect thousands of files across complex monorepo structures to classify document clusters and determine the correct migration commands.

Core Features & Use Cases

  • Read-Only Repository Survey: Walks an entire repository tree and classifies every document cluster into an adoption taxonomy without modifying any files.
  • Adoption Taxonomy Classification: Identifies five distinct buckets including already migrated projects, legacy migratable clusters, bare threads, loose documents, and foreign grammar families that require special handling.
  • Actionable Recommendations: Reports the exact command needed for each cluster, such as /anvil:project-migrate for legacy and bare clusters or /anvil:project-migrate --enroll for loose documents, enabling immediate action.

Quick Start

Use the project-scout skill to survey your repository root and receive a classified adoption report with recommended next commands for each document cluster.

Frequently Asked Questions about project-scout

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

FAQPage Schema
How do I survey a monorepo to find documents ready for migration?

To survey a monorepo for migration, you can run a read-only repository survey that walks the entire tree and classifies every document cluster into an adoption taxonomy without modifying any files.

What is an adoption taxonomy for repository document classification?

An adoption taxonomy for document classification categorizes repository files into five buckets: already migrated projects, legacy migratable clusters, bare threads, loose documents, and foreign grammar families requiring special handling.

Can I classify loose markdown and tex files in a large repository without modifying them?

Yes, you can classify loose markdown and tex files without modifying them by running a deterministic read-only survey that assesses mixed legacy and modern document structures across the repository tree.

How do I get recommended migration commands for different document clusters in a monorepo?

To get recommended migration commands for document clusters, survey the repository to receive a classified adoption report that specifies exact commands like /anvil:project-migrate for legacy clusters or /anvil:project-migrate --enroll for loose documents.

What is the best way to handle versioned thread families during a repository migration assessment?

The best way to handle versioned thread families during a repository migration assessment is to use an automated discovery tool that identifies bare threads and classifies them within an adoption taxonomy for accurate coverage accounting.

Does repository surveying account for pruned subtrees and candidate file counts in monorepos?

Yes, repository surveying produces deterministic read-only reports that provide honest coverage accounting for pruned subtrees and candidate file counts, ensuring accurate migration planning across complex monorepo structures.