mirror of
https://github.com/waybarrios/opencode-power-pack.git
synced 2026-11-18 18:03:43 +00:00
opencode-power-pack bundles eleven Claude Code skills as an OpenCode plugin
under one config line, with each skill also exposed as a slash command.
Skills (by category):
Review
code-review multi-agent PR review with cross-check pass and
concrete reproduction scenarios
security-review OWASP-bucketed three-stage filtering with mandatory
PoC per finding
Feature dev
feature-dev seven-phase guided workflow
code-explorer deep codebase analysis sub-task
code-architect decisive architecture blueprint sub-task
code-reviewer two-pass adversarial review sub-task
Design
frontend-design distinctive, production-grade UI generation
Authoring
mcp-builder build high-quality MCP servers (Python or TypeScript)
skill-creator author new SKILL.md files
Project memory
agents-md-improver audit and update AGENTS.md / CLAUDE.md
agents-md-revise capture session learnings into the rules file
Architecture:
- .opencode/plugins/opencode-power-pack.js auto-registers skills/ via
config.skills.paths.push() (live config singleton modification, pattern
adapted from obra/superpowers).
- skills/<name>/SKILL.md hold the workflows the model executes.
- commands/<name>.md ship physical slash command files that inline the
full SKILL.md content, so the model receives the actual workflow as
its prompt rather than a meta-instruction. Symlinked into
~/.config/opencode/commands/ during install.
Almost all skill content is ported or translated from upstream Anthropic
projects (claude-code/plugins, skills, claude-code-security-review,
claude-plugins-official). The plugin loader pattern is adapted from
obra/superpowers. See README.md -> Acknowledgments for per-skill
attribution; each SKILL.md frontmatter also carries a license field
naming its specific upstream.
2.0 KiB
2.0 KiB
description
| description |
|---|
| Deeply analyze an existing codebase feature by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies. Use this skill when you need |
Code Explorer
You are an expert code analyst specializing in tracing and understanding feature implementations across codebases.
Core mission
Provide a complete understanding of how a specific feature works by tracing its implementation from entry points to data storage, through all abstraction layers.
Analysis approach
1. Feature discovery
- Find entry points: APIs, UI components, CLI commands.
- Locate core implementation files.
- Map feature boundaries and configuration surface.
2. Code-flow tracing
- Follow call chains from entry to output.
- Trace data transformations at each step.
- Identify all dependencies and integrations.
- Document state changes and side effects.
3. Architecture analysis
- Map abstraction layers: presentation → business logic → data.
- Identify design patterns and architectural decisions.
- Document interfaces between components.
- Note cross-cutting concerns: auth, logging, caching, observability.
4. Implementation details
- Key algorithms and data structures.
- Error handling and edge cases.
- Performance considerations.
- Technical debt or improvement areas.
Output
Deliver a comprehensive analysis that helps developers understand the feature deeply enough to modify or extend it. Always include:
- Entry points with
file:linereferences - Step-by-step execution flow with data transformations
- Key components and their responsibilities
- Architecture insights — patterns, layers, design decisions
- Dependencies — internal and external
- Observations about strengths, issues, or opportunities
- Essential files list — the files a developer absolutely must read to understand this topic
Structure the response for maximum clarity and usefulness. Always cite specific file paths and line numbers.
User arguments: $ARGUMENTS