abildtoft/kramme:code:zoom-out
kramme-cc-workflow/skills/kramme:code:zoom-out/SKILL.md
Map the modules and call relationships in an area in focus. Use when the user is unfamiliar with a section of code and wants a one-shot orientation — modules involved, what they do, who calls what. Not for full-repo scans (use kramme:code:refactor-opportunities); not for bug investigation (use kramme:debug:investigate); not for visualizations (use kramme:visual:diagram).
$ install --global
skillsauthnpx skillsauth add abildtoft/kramme-cc-workflow kramme:code:zoom-outInstall 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 19, 2026, 5:03 AM118.7s2 files scanned
SKILL.md
- name:
- kramme:code:zoom-out
- description:
- Map the modules and call relationships in an area in focus. Use when the user is unfamiliar with a section of code and wants a one-shot orientation — modules involved, what they do, who calls what. Not for full-repo scans (use kramme:code:refactor-opportunities); not for bug investigation (use kramme:debug:investigate); not for visualizations (use kramme:visual:diagram).
- argument-hint:
- [path, topic, or symbol — optional]
- disable-model-invocation:
- true
- user-invocable:
- true
Zoom Out
Produce a one-shot orientation map for an area of the codebase: which modules live there, what each one does, and how they call each other.
Inputs
$ARGUMENTS(optional): a path, topic, or symbol naming the area to map.- If
$ARGUMENTSis empty, infer the focus area from the most recently discussed file or symbol in the conversation. If no reliable focus exists, ask the user for a path, topic, or symbol before continuing.
Workflow
- Identify the focus area. If
$ARGUMENTSis non-empty, treat it as the entry point. Otherwise infer from recent conversation context. If no reliable focus exists, ask the user for a path, topic, or symbol before continuing. State the focus area at the top of the output. - List the relevant modules in that area (≤15). For each, write
**ModuleName** — one-line role. Use the project's domain language ifUBIQUITOUS_LANGUAGE.mdexists at the repo root. - Describe call relationships as directed bullets:
**Caller** calls **Callee** to <reason>. Cover both inbound (who calls into the area) and outbound (what the area calls).
Output Format
**Focus area:** <path or topic>
## Modules
- **<Name>** — <one-line role>
## Relationships
- **<Caller>** calls **<Callee>** to <reason>
Rules
- Cap at ~15 modules. If the area is larger, list the top entries by inbound-call count and add a final line
**Omitted:** N more modules — narrow the scope to see them. - Do not propose changes. This skill produces orientation only. No fixes, refactors, or recommendations.
- No diagrams. Text map only. Use
kramme:visual:diagramfor visualizations. - Stay inside the focus area. Do not chase callers more than one hop out.
Verification
- [ ] At least one relationship listed.
- [ ] No recommended-changes section in the output.
- [ ] Output ≤ 50 lines for typical scope.
Related Skills
abildtoft/kramme:pr:verify-description
development
VerifiedTrustedCommunity
Compare an existing PR's title and body against the actual branch diff and report drift — false claims, missing major changes, stale scope, missing risk callouts. Use after pushing changes to a branch with an open PR, or before requesting review. Read-only by default; add --fix to delegate to kramme:pr:generate-description for an updated description. Complements kramme:pr:code-review (which checks description accuracy as one signal among many code-quality checks) by being a fast, focused, single-purpose check that runs in seconds.
2SKILL.mdUpdated May 31, 2026
abildtoft/kramme:skill:review
tools
VerifiedTrustedCommunity
Reviews plugin skills for focused scope, progressive disclosure, portability, safety, retry behavior, and documentation quality. Use when auditing a SKILL.md, skill directory, or proposed skill text against skill-authoring standards. Not for creating new skills, editing skills, or reviewing ordinary application code.
2SKILL.mdUpdated May 28, 2026
abildtoft/kramme:session:automate-repeats
tools
VerifiedTrustedCommunity
Reviews recent agent session transcripts to find repeated manual workflows or repeated user asks, then proposes and optionally scaffolds only useful new skills or custom subagents. Use when the user asks to inspect recent sessions, find automation opportunities, or create reusable workflows from repeated work. Not for summarizing one session, general retrospectives, or codebase refactoring.
2SKILL.mdUpdated May 25, 2026
abildtoft/kramme:siw:issue-reindex
data-ai
VerifiedTrustedCommunity
Remove all DONE issues and renumber remaining issues within each prefix group. Not for editing live issue content, archiving still-open issues, or moving issues between prefix groups.
2SKILL.mdUpdated Apr 28, 2026