lightforgelabsstudio/codebase-review
skills/codebase-review/SKILL.md
Holistic read-only codebase health review to find architecture drift, dead code, test gaps, and doc gaps.
development
Updated May 7, 2026
$ install --global
skillsauthnpx skillsauth add lightforgelabsstudio/aide codebase-reviewInstall 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: May 7, 2026, 6:52 AM123.4s1 file scanned
SKILL.md
- name:
- codebase-review
- description:
- Holistic read-only codebase health review to find architecture drift, dead code, test gaps, and doc gaps.
Codebase Review
Strategic read-only review of the codebase. Produce actionable findings. No fixes.
Inputs
Scope (domains or systems to focus on). Target branch (default main).
Review-aware
Before starting: check if <slug>.findings.md exists for this scope. If it does, build on prior findings rather than starting over.
Workflow
-
Load context — Read AGENTS.md for invariants and authoritative systems. Check GitHub activity (
gh issue list --state open,gh pr list) to identify hotspots. -
Sample strategically — Focus on:
- Recent churn areas (from git log)
- Systems flagged in open issues or PRs
- Determinism violations (anything outside logistics_tick/combat_tick)
- Duplicated systems or ambiguous authority
- Autoload/UI coupling
- Dead code or unreferenced assets
- Test coverage gaps on critical paths
-
Report — Group findings by severity (Critical/Major/Minor) with
path:lineand impact description. -
Track findings — For Critical and Major findings, create GitHub issues via
/issue. For AIDE framework findings, use/issuewith appropriate labels.
Reference
- Project invariants: AGENTS.md
- Coding patterns:
docs/CODING_GUIDELINES.md - Testing requirements:
docs/TESTING_POLICY.md
Related Skills
lightforgelabsstudio/sanity-check
testing
VerifiedTrustedCommunity
Skeptical gap analysis for issues, ADRs, plans, and docs. Use when the user wants a second-pass check for missing decisions, contradictions, edge cases, hidden dependencies, scope drift, or readiness before implementation.
SKILL.mdUpdated May 11, 2026
lightforgelabsstudio/sync
tools
VerifiedTrustedCommunity
Sync branch with remote and confirm a clean end-of-session state.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/skill-author
testing
VerifiedTrustedCommunity
Create or update an AIDE skill in .aide/skills with valid frontmatter and a concise workflow.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/scope
tools
VerifiedTrustedCommunity
Decompose an accepted ADR into GitHub issues using the issue-creator tool.
SKILL.mdUpdated May 7, 2026