This skill should be used when the user asks to "run beta test cycle", "run next cycle", "test static patterns", "analyze test failures", "improve pass rate", or wants to systematically improve command generation quality through iterative testing and pattern refinement. Provides structured workflow for running test cycles, analyzing failures, implementing fixes, and documenting results.
Aligns versions across multiple repositories according to release strategy (lockstep, independent, umbrella). Handles semantic versioning constraints, detects version conflicts, suggests version bumps based on conventional commits, validates cross-repo compatibility, manages version matrices for umbrella releases. Activates for version alignment, align versions, version sync, semver, version conflicts, version bump, version compatibility, cross-repo versions, umbrella version matrix, lockstep versioning.
Guide for running and validating quality gates (build, lint, test, coverage, regression). Use when validating code, running tests, or checking if a phase can proceed.
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
Default technology stack for Gaia projects. Use when starting new projects, making tech decisions, or setting up infrastructure. These are defaults and as such, any specific user mandates for any of the below areas, should be honored.
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
Ship features safely with progressive rollouts, feature flags, and canary deployments. Use when deploying risky features or need gradual rollouts.
Analyze GitHub issues, view PR details, fetch repository info, check CI status, get issue comments. Use when user mentions GitHub URLs, issue/PR numbers (#123), or asks about PRs/issues.
Perform comprehensive code reviews using OpenAI Codex CLI. This skill should be used when users request code reviews, want to analyze diffs/PRs, need security audits, performance analysis, or want automated code quality feedback. Supports reviewing staged changes, specific files, entire directories, or git diffs.
Template for creating skills. Use when writing new code, reviewing code, or when the skill's specific domain applies. Replace this description with specifics.
Guide for using Gaia's MCP memory tools (remember/recall) with session-level and persistent storage. Use when debugging, implementing features, or making decisions.
Detect and document existing code patterns in a codebase. Use to maintain consistency with established conventions when writing new code.
Validates code changes against the project's consolidated knowledge and configuration rules. Use on push to catch violations of agreed-upon standards like installation scripts, linking patterns, and configuration consistency.
Run comprehensive validation and review checks including heading numbering, TODO/FIXME comments, Nextflow script conventions, orphaned files, admonition syntax, lesson structure, formatting, content accuracy, and teaching effectiveness. Use when validating, reviewing, or checking training materials quality, lesson quality, or before committing changes.
Review code for quality, security, performance, and maintainability. Auto-activate after code modifications.
Code Simplifier - Refines code for clarity, consistency, and maintainability while preserving exact functionality. Based on Anthropic's official code-simplifier. Focuses on recently modified code unless instructed otherwise. Activates for simplify code, clean up code, refactor for clarity, reduce complexity, improve readability.
Coding standards discovery agent. Performs deep analysis of codebase to detect naming conventions, import patterns, function characteristics, type usage, error handling, and anti-patterns. Generates evidence-based coding standards documentation with statistical confidence levels and real code examples. Parses ESLint, Prettier, TypeScript configs. Detects security issues and maintainability concerns. Activates for coding standards, code conventions, naming conventions, style guide, code analysis, detect patterns, import patterns, function patterns, type patterns, error handling patterns, anti-patterns, eslint config, prettier config, typescript config, code style, code quality rules, project conventions, consistency check, coding guidelines.
Validate feature doc format against .patterns/feature-docs.md. Use when reviewing PRs, after editing feature docs, or before commits
Use when implementing authentication in Bknd, configuring auth strategies (password, OAuth, email OTP), managing sessions with JWT/cookies, creating users, and protecting endpoints. Covers auth module configuration, user management, and security best practices.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
