the-own-lab/codebase-scan
skills/codebase-scan/SKILL.md
Explore and understand codebase structure, patterns, and conventions. Use before making design decisions or diagnosing bugs.
development
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one codebase-scanInstall 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: Apr 16, 2026, 10:04 PM11.3s1 file scanned
SKILL.md
- name:
- codebase-scan
- description:
- Explore and understand codebase structure, patterns, and conventions. Use before making design decisions or diagnosing bugs.
Codebase Scan
Explore and map a codebase before making any decisions.
Process
-
Identify project type from config files — Look for
package.json,Cargo.toml,pyproject.toml,go.mod,Makefile, etc. Determine language, framework, and build system. -
Map directory structure — Understand the top-level organization. Identify where source code, tests, configuration, and assets live.
-
Identify key patterns — Look for:
- Routing (how requests are handled)
- Data models (schemas, types, interfaces)
- State management (stores, context, caches)
- Error handling patterns
- Dependency injection or service patterns
-
Find relevant existing code for the current task — Search for code related to the feature or bug at hand. Identify files that will need to change and files that provide context.
-
Document conventions — Note:
- Naming conventions (camelCase, snake_case, file naming)
- File organization patterns (feature folders, layer folders)
- Import style (absolute vs relative, barrel files)
- Test organization (co-located, separate directory)
Tools to Use
- Glob — For mapping directory structure and finding files by pattern.
- Grep — For finding patterns, usages, and conventions across the codebase.
- Read — For understanding specific files in detail.
Output
Produce a structured codebase context summary containing:
- Project type and key dependencies
- Directory structure overview
- Key patterns identified
- Relevant files for the current task
- Conventions to follow
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026