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:linear:issue-to-pr
tools
VerifiedTrustedCommunity
Requires Linear MCP. Implements one Linear issue end to end, selects applicable code-review, convention, and PR-refactor gates, runs them to bounded convergence, verifies, and optionally opens the PR and iterates on CI and review feedback until green. Use when the user wants a single Linear issue taken from implementation through a clean Pull Request. Not for implementation-only work, SIW-tracked issues, stacked PRs, existing PR updates, or post-merge rollout.
2SKILL.mdUpdated Jul 28, 2026
abildtoft/kramme:pr:convention-review
development
VerifiedTrustedCommunity
Reviews PR and local changes for convention drift and overcaution against documented rules and mined peer-file practice. Use for new patterns, dependencies, abstractions, or defensive complexity that departs from established practice; every finding cites evidence. Supports --inline. Not for general code quality (use kramme:pr:code-review) or spec review (use kramme:siw:spec-audit --team).
2SKILL.mdUpdated Jul 16, 2026
abildtoft/kramme:siw:wayfinder
testing
VerifiedTrustedCommunity
Charts huge or foggy initiatives into a local `.context` decision map and resolves one typed frontier ticket per session until the work is ready for SIW or another execution workflow. Use when the route to a destination cannot fit in one agent session or parallel workspaces need coordinated planning state. Not for clear specs, ordinary issue decomposition, implementation, or Linear-native tracking.
2SKILL.mdUpdated Jul 11, 2026
abildtoft/kramme:research
development
VerifiedTrustedCommunity
Investigates a question against primary sources and saves one cited Markdown artifact. Use for reading legwork: official docs/API facts, source-code or spec checks, standards, and first-party service behavior before planning or implementation. Not for making product or architecture decisions, implementing code, broad web search, secondary blog summaries, or uncited answers.
2SKILL.mdUpdated Jul 10, 2026