Discover devops cicd skills, compare source repositories and read the instructions for each workflow.
Replaces the entire process of formulating implementation plans and integrating results based on detailed specifications through Test-Driven Development (TDD). Typical use cases: (1) Decomposing detailed specif...
Orchestrates the Code Review process (Analysis -> Fix -> Reply/Close). Manages the workflow by invoking specialized sub-skills like code-review-analysis, tdd-refactoring, and tdd-audit. Used for (1) addressing...
Analyzes existing code and specs to identify missing test coverage and formulate a robust Testing Plan. Used for adding regression tests, increasing coverage, and verifying legacy code behavior.
Audits the architecture visualization plan (Common Definitions & Draft Issues) before execution. Strictly enforces SYSTEM_ARCHITECT values and ensures zero regressions by validating against loaded SSOT context...
Decomposes approved ADRs/Design Docs into a dependency graph of Artifacts and Tasks using backward chaining. Generates a robust roadmap where every task is logically connected to existing assets.
Replaces the entire process of formulating Architecture Decision Records (ADRs) based on the OODA loop. Typical use cases: (1) Defining the specific scope and components of the system to be implemented next, (2...
Skill for auditing .gemini/todo.md to ensure tasks are atomic, verifiable, and logically sound. Checks for gaps, jumps in logic, and missing verification steps.
Workflow patterns from go-agents-orchestration library. Use when implementing workflows, state management, checkpoints, or parallel processing. Triggers: StateGraph, workflows.Register, WorkflowFactory, state.S...
Detect divergence between specifications and implementation during development. Use during implementation phases to identify scope creep, missing features, contradictions, or extra work not in spec. Logs drift...
Create and validate implementation plans (PLAN). Use when planning implementation phases, defining tasks, sequencing work, analyzing dependencies, or working on implementation-plan.md files in docs/specs/. Incl...
Initialize and manage specification directories with auto-incrementing IDs. Use when creating new specs, checking spec status, tracking user decisions, or managing the docs/specs/ directory structure. Maintains...
Automatic code review for pull requests and commits
Document how to group Laravel seeders between local and shared environments, ensure seeders guard against duplication, and keep reruns safe.
Run eval snapshots, checks, or reports for Operator's Edge.
Use when working with Ansible Core 2.19 for automation, configuration management, playbooks, modules, or infrastructure as code (project)
Deploy applications to Cloudflare Workers and/or Supabase Edge Functions. Supports unified multi-platform deployment. Use when deploying to production, publishing APIs/functions, or when user requests deploymen...
Deploy applications to Cloudflare Workers and/or Supabase Edge Functions. Supports unified multi-platform deployment. Use when deploying to production, publishing APIs/functions, or when user requests deploymen...
Runs checks per AGENTS.md and writes the verification transcript to tasks/20_verification.md.
Implement a plan from a specification file
Generate exhaustive user-flow and edge-case test scenarios from an app's codebase, produce scenario .md files, execute tests using connected or newly created MCPs, and produce an app.qa.report.md summarizing fa...
Verify project configuration before using other skills/agents. Creates .claude/project.json if missing.
Reviews code changes for bugs, style issues, security, and best practices. Use when reviewing PRs or checking code quality.
Git workflow guidance including branching, commits, and collaboration. Use when asked about git operations or workflow.
Use the Epic CLI for project management, issue tracking, PR workflows, git worktrees, and debugging. Triggers on requests like "create a project", "start an issue", "work on PR", "create worktree", or "add debu...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.