jarvis-codebase-mapper-01
Map unfamiliar codebases into modules, owners, and entrypoints.
Setup & Installation
Install command
clawhub install xammarie/jarvis-codebase-mapper-01If the CLI is not installed:
Install command
npx clawhub@latest install xammarie/jarvis-codebase-mapper-01Or install with OpenClaw CLI:
Install command
openclaw skills install xammarie/jarvis-codebase-mapper-01or paste the repo link into your assistant's chat
Install command
https://github.com/openclaw/skills/tree/main/skills/xammarie/jarvis-codebase-mapper-01What This Skill Does
A structured workflow agent for development tasks on unfamiliar codebases. It takes a desired outcome, constraints, and available artifacts, then returns ranked findings, an action plan, and concrete checklists. Each step runs through quality gates that require evidence-backed claims and explicit tradeoffs.
Unlike ad-hoc debugging, it enforces evidence-backed claims and explicit fallback plans at each checkpoint, reducing rework from assumptions that turn out wrong.
When to Use It
- Onboarding to a new codebase before submitting a pull request
- Planning a risky refactor with fallback steps defined upfront
- Converting messy notes or requirements into a prioritized action plan
- Running pre-release quality checks with defined acceptance criteria
- Delegating a debugging task with a clear owner and ETA for each step
View original SKILL.md file
# Jarvis Codebase Mapper 01 Deliver a concrete, reusable workflow for development tasks. ## Inputs - Desired outcome and deadline - Constraints (time, tools, risk tolerance) - Available artifacts (code, docs, screenshots, logs) ## Playbook 1. Define success and failure criteria in measurable terms. 2. Build a smallest-valid execution path before scaling effort. 3. Execute in checkpoints; record evidence at each checkpoint. 4. Apply quality gates before finalizing recommendations. 5. Return implementation-ready outputs and next actions. ## Quality Gates - Evidence-backed claims only. - Explicit assumptions and tradeoffs. - Reversible changes preferred for risky operations. - Clear owner + ETA for each next step. - Include a fallback if the primary plan fails. ## Output Format - Situation summary (5 lines max) - Top findings (ranked by impact) - Action plan (today / this week) - Risks + mitigations - Exact checklist or commands where useful ## Example prompts - "Use this skill to turn my messy notes into a production-ready plan." - "Run this skill and give me a risk-first action sequence with acceptance checks."
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Onboarding to a new codebase before submitting a pull request
- 1Onboarding to a new codebase before submitting a pull request
- 2Planning a risky refactor with fallback steps defined upfront
- 3Converting messy notes or requirements into a prioritized action plan
- 4Running pre-release quality checks with defined acceptance criteria
- 5Delegating a debugging task with a clear owner and ETA for each step
Map unfamiliar codebases into modules, owners, and entrypoints.
Security Audits
These signals reflect official OpenClaw status values. A Suspicious status means the skill should be used with extra caution.