code-explorer
Code-explorer traces how a specific feature executes through a codebase by mapping entry points, following call chains from user interaction to data storage, and documenting all abstraction layers and dependencies. Use it when investigating an unfamiliar feature before modifying it, during feature development workflows, or whenever understanding existing implementation patterns is necessary for safe changes.
git clone --depth 1 https://github.com/waybarrios/opencode-power-pack /tmp/code-explorer && cp -r /tmp/code-explorer/skills/code-explorer ~/.claude/skills/code-explorerSKILL.md
# 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:line` references - **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.
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or when the codebase has changed enough that the rules file may be stale. Scans the repository for every rules file, grades each against a quality rubric, outputs a quality report, and applies targeted edits only after user approval.
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end of a productive session when valuable context has emerged that is not yet documented. This is the COMPLEMENT to agents-md-improver: improver audits, this one captures.
Design a feature architecture by analyzing existing codebase patterns and conventions, then provide a comprehensive implementation blueprint with specific files to create or modify, component designs, data flows, and a build sequence. Use this skill when the user asks for an architecture design, an implementation plan for a non-trivial feature, or when dispatched as a sub-task during feature-dev architecture phase.
Review a pull request or a set of code changes for bugs, logic errors, and project-convention violations using a confidence-filtered, multi-agent process. Use this skill when the user asks to review a PR, audit pending changes, or inspect a diff for problems before merging.
Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a sub-task during feature-dev quality review, or when the user wants a critique of a specific file or function.
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than diving straight to code.
Create distinctive, production-grade frontend interfaces with high design quality and accessible markup. Use this skill when the user asks to build or beautify web components, pages, applications, landing pages, dashboards, artifacts, or React/HTML/CSS UI. Generates creative, polished code that avoids generic AI aesthetics, then self-checks it against an objective accessibility and quality rubric.
Guide the creation of high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when the user wants to build an MCP server to integrate an external API or service, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).