Loading...
Loading...
Found 64 Skills
Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
Local Code Review - analyzes code changes and provides structured feedback before commit
A senior Odoo developer agent, expert in Odoo framework, Python, XML, PostgreSQL, and best practices (OCA/Odoo Guidelines).
Three-lens code review using parallel subagents: Epimetheus (hindsight — bugs, debt, fragility), Metis (craft — clarity, idiom, fit-for-purpose), Prometheus (foresight — vision, extensibility, future-Claude). Triggers on /titans, /review, 'review this code', 'what did I miss', 'before I ship this'. Use after completing substantial work, before /close. (user)
Adaptive test-driven development cycle. Detects harness capabilities and routes to guided (manual phase control) or automated (orchestrated) mode. Invoke with /tdd for automated or /tdd red|domain|green|commit for guided.
Perform systematic self-review of code changes before commits using structured checklist. Validates architecture boundaries, code quality, test coverage, documentation, and project-specific anti-patterns. Use before committing, creating PRs, or when user says "review my changes", "self-review", "check my code". Adapts to Python, JavaScript, TypeScript, Go, Rust projects.
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
This skill should be used when the user requests actions such as 'review code', 'do a code review', 'review my branch', 'review MR !1234', or 'review PR'
Defense-in-depth verification before declaring any task complete. Run tests, check build, validate changed files, verify no regressions. Applies 4-level adversarial artifact verification (EXISTS > SUBSTANTIVE > WIRED > DATA FLOWS) with goal-backward framing. Use before saying "done", "fixed", or "complete" on any code change. Use for "verify", "make sure it works", "check before committing", or "validate changes". Do NOT use for debugging (use systematic-debugging) or code review (use systematic-code-review).
Fresh-subagent-per-task execution with two-stage review (ADR compliance + code quality). Use when an implementation plan exists with mostly independent tasks and you want quality gates between each. Use for "execute plan", "subagent", "dispatch tasks", or multi-task implementation runs. Do NOT use for single simple tasks, tightly coupled work needing shared context, or when the user wants manual review after each task.
Use OpenAI's Codex CLI as an independent code reviewer to provide second opinions on code implementations, architectural decisions, code specifications, and pull requests. Trigger when users request code review, second opinion, independent review, architecture validation, or mention Codex review. Provides unbiased analysis using GPT-5-Codex model through the codex exec command for non-interactive reviews.
Bug Fixing Skill - Read bugs/pending.csv to select bugs and automatically execute the 8-stage repair process