skills.rest
mnazaal
mnazaalCOMMUNITY
Explore all skills by this author →
Website𝕏@mnazaaIGitHub

dev-scout

Maps repository architecture, entry points, interfaces, and risks through read-only exploration.

Updated Jul 3, 2026
Search Tags:#technical debt#code audit#codebase exploration#repository analysis#read-only#entry points#architecture mapping
One-click install
npx skills add https://github.com/mnazaal/dotfiles --skill dev-scout-mnazaal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-scout
Source: https://github.com/mnazaal/dotfiles/tree/main/.agents/skills/dev-scout
Command: npx skills add https://github.com/mnazaal/dotfiles --skill dev-scout-mnazaal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When joining an unfamiliar codebase or evaluating a repository, developers waste hours clicking through directories trying to understand architecture, entry points, and hidden risks. This Skill performs structured read-only reconnaissance and delivers a concise architecture report without touching any code. ## Core Features & Use Cases - Architecture Mapping: Reads READMEs, configs, CI files, lockfiles, and tests to map directory structure, entry points, and key modules. - Gap Detection: Cross-checks documented API claims against actual code to surface documented-but-unimplemented features, missing tests, and stale docs. - Risk Identification: Identifies interfaces, adapters, generated directories, fragile assumptions, and sticky parts of the codebase. - Use Case: You inherit a legacy service with sparse documentation. Run this Skill to get an architecture overview, entry points, key seams, and a list of risks before writing a single line of code. ## Quick Start Scout this repository and report its architecture, entry points, key interfaces, sticky parts, and gaps.

Frequently Asked Questions about dev-scout

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

FAQPage Schema
How do I understand an unfamiliar codebase quickly?▼

Use a structured scouting workflow: read project signals like README, configs, and CI files first, then map directory structure and entry points, and trace one or two key flows end to end. This Skill automates that process and reports architecture, interfaces, and risks.

How to audit a repository without modifying code?▼

This Skill operates strictly read-only, exploring architecture, entry points, tests, and configs without editing anything. It surfaces findings and gaps rather than implementing fixes, routing implementation work to separate development skills.

Can this detect documented features that are not implemented?▼

Yes. The Skill cross-checks headline documentation and README API claims against the actual code. A documented-but-unimplemented or stale feature is treated as a top-tier gap in the final report.

Does repo scouting work on logs or transcripts instead of a checkout?▼

Yes. When scouting an ingested artifact like a log, transcript, or terminal dump, the Skill preserves timestamps and file references in its report and explicitly states what the artifact could not show.

What are the limitations of read-only codebase exploration?▼

Read-only scouting cannot debug, run, or fix code; it only reports findings. Suspicious broken paths are routed to debugging skills and implementation gaps to development skills, so follow-up work requires those separate tools.

Related Skills

Explore More Software Engineering Skills→
mitsuhikomitsuhiko
3.0k

librarian

Cache and refresh remote git repositories under a stable local checkout path.

Community
Intermediate
MercurykzMercurykz

codenavi

Navigate unfamiliar codebases and document findings in a .notebook/ knowledge base.

Community
Advanced
Space-DinosaursSpace-Dinosaurs
12

test-suite-comprehension

Map source modules to tests and produce a ranked coverage gap report.

Official
Advanced
adobeadobe

config-authoring

Configure and harden Adobe AEM Cloud Dispatcher and HTTPD configurations.

Official
Advanced