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".
npx skillsauth add microsoft/github-copilot-modernization project-reconInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Quickly answers: how big is this repo and what's in it. Shell-only (POSIX find + wc or PowerShell), runs anywhere, no install needed.
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-dir succeeds)Do NOT add fields beyond this schema. No descriptions, no module lists, no domain analysis.
| 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 |
language-extensions.yaml for the canonical extension list.exclude-patterns.yaml::global.dirs with per_language.<lang>.dirs for each detected language.references/loc-shell.md. Run once per detected language, sum for total.wc -l), comment-inclusive. This is intentional — speed and simplicity over precision.development
Scan dependency manifests against known CVEs and remediate by upgrading vulnerable dependencies to patched versions, then rebuild and re-scan to confirm. Self-contained scan→fix→verify loop for any project with a dependency manifest. Use when: a cve-remediation task is dispatched; dependency set changed (version bump, new framework); assessment flagged vulnerable or EOL dependencies; or user asked to "fix CVEs", "patch vulnerabilities", or "dependency security". Triggers: "cve", "remediate cve", "fix cves", "patch vulnerable dependencies", "vulnerability scanning", "dependency security", "vulnerable dependencies", "security advisories", "npm audit", "pnpm audit", "maven audit", "gradle audit", "dependency scan", "vulnerability remediation". NOT for: security audit of auth/input/secrets/OWASP code paths (use security-review).
development
Generate dependency map diagram from project build files
documentation
Generate data architecture and persistence layer documentation with data model diagram
documentation
Generate core business workflow documentation with sequence diagram