Jarvis Codebase Mapper 01

Map unfamiliar codebases into modules, owners, and entrypoints. Use when handling development work that needs repeatable steps, quality gates, and practical...

Security Scan

This is an instruction-only playbook for mapping codebases; its declared purpose matches the contained instructions and it requests no installs, files, or credentials.

Purpose & Capability

The name/description (map codebases to modules, owners, entrypoints) aligns with the SKILL.md playbook and output format. Nothing in the metadata asks for unrelated resources (no env vars, binaries, or config paths).

Instruction Scope

SKILL.md contains a high-level, structured workflow (inputs, playbook steps, quality gates, output format). It does not instruct the agent to read system files, access environment variables, call external endpoints, or perform arbitrary code execution. It does expect the user to provide artifacts (code, docs, logs) which is appropriate for the stated purpose.

Install Mechanism

No install spec and no code files — instruction-only. No downloads, package installs, or extracted artifacts are requested, so there is minimal installation risk.

Credentials

The skill declares no required environment variables, credentials, or config paths. This is proportionate for an advisory/playbook skill that produces mapping and action plans.

Persistence & Privilege

always:false and the skill does not request persistent system presence or permissions. It does not modify other skills or system configs and does not require autonomous invocation privileges beyond the platform default.

Assessment

This skill is low-risk: it's an instruction-only playbook for producing plans and checklists and requests nothing from your environment. Before using it, avoid uploading sensitive secrets or private keys as input; only provide the code/artifacts necessary for the mapping task. If you want the agent to run commands or modify repositories automatically, that requires additional tooling or plugins — which increases risk and should be reviewed. Finally, treat outputs as guidance: verify suggested commands, owners, and changes before applying them in your environment.

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."