a5c-ai/codebase-research
library/methodologies/rpikit/skills/codebase-research/SKILL.md
Systematic codebase exploration following the Iron Law - understand the problem before exploring code. Four phases with file-finder and web-researcher agents.
$ install --global
skillsauthnpx skillsauth add a5c-ai/babysitter codebase-researchInstall 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 1, 2026, 12:10 PM56.3s2 files scanned
SKILL.md
- name:
- codebase-research
- description:
- Systematic codebase exploration following the Iron Law - understand the problem before exploring code. Four phases with file-finder and web-researcher agents.
- allowed-tools:
- Read, Write, Edit, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion
Codebase Research
Overview
Perform systematic codebase exploration to understand how existing systems work. Follows the Iron Law: "Do NOT explore the codebase until the problem is understood."
When to Use
- Implementation direction is clear but codebase understanding is needed
- Investigating how an existing feature works before modifying it
- Understanding dependencies and data flows before planning
- Gathering context for a known goal
Process
- Understand the request - Ask clarifying questions one at a time (purpose, specifics, scope, constraints, context). Do NOT read any files until confirmed.
- Explore the codebase - Use file-finder agent, read in order, trace data flows, identify constraints.
- Document findings - Write structured research document to
docs/plans/YYYY-MM-DD-<topic>-research.md. - Transition - Ask: plan, continue research, or conclude.
Key Rules
- Quotations from source material capped at 125 characters maximum
- Only proceed to exploration after human confirms understanding
- Use file-finder agent for initial file discovery
- Use web-researcher agent for external context needs
Agents Used
agents/file-finder/- Locates relevant files with suggested reading orderagents/web-researcher/- Gathers external context when needed
Tool Use
Invoke via babysitter process: methodologies/rpikit/rpikit-research
Related Skills
a5c-ai/model-card-generator
development
VerifiedTrustedCommunity
Model documentation skill for generating model cards following Google's model card framework.
680SKILL.mdUpdated Apr 28, 2026
a5c-ai/mlflow-experiment-tracker
development
VerifiedTrustedCommunity
MLflow integration skill for experiment tracking, model registry, and artifact management. Enables LLMs to log experiments, compare runs, manage model lifecycle, and retrieve artifacts through the MLflow API.
680SKILL.mdUpdated Apr 28, 2026
a5c-ai/lime-explainer
data-ai
VerifiedTrustedCommunity
LIME-based local explanation skill for individual predictions across tabular, text, and image data.
680SKILL.mdUpdated Apr 28, 2026
a5c-ai/kubeflow-pipeline-executor
devops
VerifiedTrustedCommunity
Kubeflow Pipelines skill for ML workflow orchestration, component management, and Kubernetes-native ML.
680SKILL.mdUpdated Apr 28, 2026