microsoft/project-recon
plugins/github-copilot-modernization/skills/project-recon/SKILL.md
Zero-dependency shell recon for any code repository — detect languages, count LOC, and report project scale. Pure POSIX find/wc or PowerShell, no Python or third-party tools required. Triggers: "how big is this project", "what languages", "project sizing", "repo recon", "LOC count", "scope check".
$ install --global
skillsauthnpx skillsauth add microsoft/github-copilot-modernization project-reconInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 8:56 AM218.5s4 files scanned
SKILL.md
- name:
- project-recon
- description:
- |
- Triggers:
- how big is this project", "what languages", "project sizing", "repo recon", "LOC count", "scope check".
Project Recon: Zero-Dependency Repo Sizing
What this skill does
Quickly answers: how big is this repo and what's in it. Shell-only (POSIX find + wc or PowerShell), runs anywhere, no install needed.
Output Format
Emit exactly this JSON structure — no additional fields:
{
"total_loc": <int>,
"languages": { "<lang>": <loc>, ... },
"top_level_dirs": <int>,
"primary_language": "<lang with highest LOC>",
"git": <bool>
}
total_loc: sum of non-blank lines across all detected source fileslanguages: per-language LOC breakdown (only languages actually found)top_level_dirs: count of immediate subdirectories under repo root (excluding hidden dirs)primary_language: the language key with the highest LOCgit: whether the project root is a git repository (git rev-parse --git-dirsucceeds)
Do NOT add fields beyond this schema. No descriptions, no module lists, no domain analysis.
Files
| File | Purpose |
|------|---------|
| references/language-extensions.yaml | Language → file extension mapping + generated-file suffixes to skip |
| references/exclude-patterns.yaml | Directory exclude rules (global + per-language) |
| references/loc-shell.md | bash + PowerShell counting templates |
Workflow
- Detect languages. Scan for manifest files (pom.xml, *.csproj, package.json, go.mod, etc.) or dominant extensions. Look up
language-extensions.yamlfor the canonical extension list. - Resolve excludes. Union
exclude-patterns.yaml::global.dirswithper_language.<lang>.dirsfor each detected language. - Count. Use the template from
references/loc-shell.md. Run once per detected language, sum for total. - Emit JSON. Output the schema above. Nothing else.
Semantics
- Counts non-blank lines (
wc -l), comment-inclusive. This is intentional — speed and simplicity over precision. - Expect 5–15% upward bias vs comment-stripping counters on verbose languages (Java, C#). Acceptable for sizing.
Related Skills
microsoft/clarifying-scenarios
development
VerifiedTrustedCommunity
Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, asks the user for missing required fields via a structured form, and writes a canonical `clarification.md` artifact consumed by all downstream agents. Triggers: "clarification gate", "scenario clarification", "elicit missing context", "evaluate prompt completeness", "ask user for screenshots / target library / design system". NOT for: feature specification (use feature-inventory), planning (use creating-implementation-plan), implementation (use implementing-code), or resolving spec-time `[NEEDS CLARIFICATION]` markers (those remain owned by feature-inventory).
12SKILL.mdUpdated Jun 4, 2026
microsoft/appmod-hooks
tools
VerifiedTrustedCommunity
Lifecycle hooks for the modernize-rearchitecture coordinator. Defines hook points, registered actions, and execution rules.
12SKILL.mdUpdated Jun 4, 2026
microsoft/team-charters
development
VerifiedTrustedCommunity
Provides role charters (mission, ownership, core principles, quality bar) for a multi-agent coding team. Each charter defines the role's mission, ownership scope, core principle (boundary constraints), and quality bar. Most roles also include communication rules. Consumed by the coordinator during task decomposition to assign work to the correct role. Triggers: "look up role charter", "what does the architect own", "check role boundaries", "find team roles", "which role handles X", "list agent charters", "role responsibilities". NOT for: task decomposition (use breaking-down-tasks), implementation (use implementing-code), architecture analysis (use analyzing-architecture).
12SKILL.mdUpdated May 14, 2026
microsoft/list-plans
data-ai
VerifiedTrustedCommunity
Discovers valid migration plans in the workspace and returns the selected plan path. A valid plan is a subdirectory of .github/modernize/ that contains plan.md AND tasks.json (tasks.json may be in the plan folder or in a .metadata subfolder). Handles 0, 1, or multiple plans and prompts the user when a choice is needed. Triggers: "list plans", "find plans", "select plan", "list-and-select-plan", "discover plans".
12SKILL.mdUpdated May 14, 2026