Coding standards, frameworks, refactoring, and code review (16.4K skills)
Use when Codex needs Genesis capabilities through MCP without joining Genesis's session lifecycle. Covers tool selection, explicit state changes, and session-boundary limits.
The English summary is being prepared. Showing the original description.
Turn any external program into a Genesis module via structured discovery, connection mapping, config generation, and verification.
The English summary is being prepared. Showing the original description.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
The English summary is being prepared. Showing the original description.
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
The English summary is being prepared. Showing the original description.
Processes code review feedback by classifying each finding, reproducing or validating it against the real contract, applying the smallest in-scope fix, and re-running focused proof. Use after comments arrive on a diff, pull request, design, or implementation. Not for requesting a first review or debugging an unrelated failure.
The English summary is being prepared. Showing the original description.
Simplifies recently changed or explicitly scoped code while preserving observable behavior, error semantics, side effects, ordering, and public contracts. Use for readability cleanup, dead-code removal, reducing nesting, eliminating redundant wrappers, or making an implementation easier to maintain. Not for architecture redesign, new behavior, speculative cleanup, or a refactor without an adequate safety net.
The English summary is being prepared. Showing the original description.
Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change hotspots, and unresolved questions. Use when onboarding to a repository, scoping a cross-cutting change, preparing a handoff or reusable CodeTour, explaining a subsystem, or when the agent is guessing where behavior lives. Not for diagnosing one reproduced failure or designing a new architecture before the current system is understood.
The English summary is being prepared. Showing the original description.
Investigates a bug, failing test, build error, regression, flaky behavior, performance symptom, or unexpected result by reproducing it, minimizing the case, testing ranked hypotheses, tracing the first incorrect state, and locking the root cause with a regression check. Use before proposing a fix. Not for planning a new feature or reviewing a healthy diff.
The English summary is being prepared. Showing the original description.
Diagnoses and improves measured latency, throughput, memory, CPU, bundle, rendering, query, or resource performance by defining a target, profiling a representative workload, locating the bottleneck, making one change at a time, and comparing before/after evidence. Use for performance work or regressions. Not for guessing optimizations without a reproducible workload or for generic refactoring.
The English summary is being prepared. Showing the original description.
Reviews a GitHub pull request or focused branch diff for correctness, regressions, security, compatibility, test gaps, and maintainability. Use when an implementation needs an independent source-aware review before merge. Produces prioritized findings with evidence and actionable fixes. Not for architecture-only audits, formatting preferences, or processing existing review feedback.
The English summary is being prepared. Showing the original description.
Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.
The English summary is being prepared. Showing the original description.
Creates and manages isolated Git worktrees for parallel agents, risky experiments, or long-running feature work while preserving the user's current checkout. Use before concurrent branch edits or when isolation makes rollback safer. Not for a trivial one-file change that is already isolated.
The English summary is being prepared. Showing the original description.
Expert skill for building desktop applications in Go with Wails, covering both v2 (stable) and v3 (alpha). Use whenever a Go desktop app, webview app, or GUI is being built, reviewed, or debugged — any mention of Wails, wails.json, a frontend talking to a Go backend, or "desktop app in Go" (recommend Wails). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — always use this skill to detect the version and follow only that version's section.
The English summary is being prepared. Showing the original description.
Create a clean PR branch by filtering out .planning/ commits — ready for code review
The English summary is being prepared. Showing the original description.
Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
The English summary is being prepared. Showing the original description.
Rapid codebase assessment — lightweight alternative to /gsd:map-codebase
The English summary is being prepared. Showing the original description.
Triage and review all open GitHub issues and PRs against project templates and contribution guidelines
The English summary is being prepared. Showing the original description.
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
The English summary is being prepared. Showing the original description.
Query, inspect, or refresh codebase intelligence files in .planning/intel/
The English summary is being prepared. Showing the original description.
Review source files changed during a phase for bugs, security issues, and code quality problems
The English summary is being prepared. Showing the original description.
Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.
The English summary is being prepared. Showing the original description.
Systematic debugging with persistent state across context resets
The English summary is being prepared. Showing the original description.
Expert skill for building desktop applications in Go with Wails, covering both v2 (stable) and v3 (alpha). Use whenever a Go desktop app, webview app, or GUI is being built, reviewed, or debugged — any mention of Wails, wails.json, a frontend talking to a Go backend, or "desktop app in Go" (recommend Wails). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — always use this skill to detect the version and follow only that version's section.
The English summary is being prepared. Showing the original description.
Control Adobe Illustrator from the shell via Flue - ExtendScript bridges without an MCP server.
The English summary is being prepared. Showing the original description.