Найдите подходящую возможность для вашего агента.
Pre-flight checks for Railway deployments to catch failures BEFORE deploying. Use when about to deploy to Railway, Railway deployment fails, debugging Railway errors, or user says "deploy to railway", "railway up", "check railway".
Evidence-based completion claims. Use before claiming work is complete, fixed, or passing - requires running verification commands and confirming output before any success claims.
Audit a repository/project for security practices, CI/CD workflow safety, adherence to project instructions (AGENTS.md/CONTRIBUTING/SECURITY), and consistency across code/config/docs. Use when preparing for release, reviewing GitHub Actions workflows, enforcing engineering guardrails, or assessing delivery readiness and governance.
Single source of truth for repository structure and entry points, including key directories, domain boundaries, shared code, integrations, and build/deploy references
Use when working with git operations - generates smart commit messages (present tense, imperative), manages branches, creates PRs with summaries, follows git best practices. Activates when user says "commit this", "create PR", "push changes", mentions "git", "branch", "merge", or before committing code.
Generate intelligent, non-redundant test plans based on implementation changes. This skill should be used after implementing features to create comprehensive yet efficient test plans with proper coverage across unit, integration, API, and E2E tests without duplication.
Reviews code changes for bugs, style issues, security, and best practices. Use when reviewing PRs or checking code quality.
Deploys AWS infrastructure with research-first approach. Uses AWS MCP tools for documentation, regional availability, and resource management. ALWAYS searches AWS documentation before writing code, explains services and abbreviations, considers alternatives, maintains organized aws/ folder, and CRITICALLY offers to destroy resources after testing. Use PROACTIVELY for any AWS deployment, Terraform, ECS, Fargate, Lambda, S3, RDS, or cloud infrastructure tasks. MUST BE USED for prototype/learning projects to avoid unexpected costs. (project)
Generates a structured handoff artifact with guard rails.
Validates BAZINGA completion claims with independent verification. Spawned ONLY when PM sends BAZINGA. Acts as final quality gate - verifies test failures, coverage, evidence, and criteria independently. Returns ACCEPT or REJECT verdict.
Build the AIQ iOS project to verify compilation succeeds. Use this skill to confirm code changes compile correctly before running tests or committing.
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 README.md in each spec to record decisions (e.g., PRD skipped), context, and progress. Orchestrates the specification workflow across PRD, SDD, and PLAN phases.
Deployment strategies for Go applications. Use when deploying applications.
Check deployment status on Orange Pi - container health, logs, and service status. Use when checking if deployment succeeded, debugging production issues, verifying services are running, or when user asks "is it running", "check prod", "deployment status", "are services up", or "production health".
Test execution, coverage analysis, and test failure debugging. Use for running tests, analyzing results, and fixing failures.
Deploy GitHub repositories to remote servers via SSH. Claude reads the README, understands build/start instructions, and executes deployment commands over SSH. Supports rollback on failure.
Validate production batch execution - trigger daily runs and analyze traces for architecture completeness and result quality
Orchestrates the Testing Strategy & Implementation process (Planning -> Execution -> Closing). Manages the workflow by invoking specialized sub-skills like code-testing-planning, tdd-refactoring, and tdd-audit. Used for (1) adding missing coverage for legacy code, (2) reproducing reported bugs with regression tests (xfail), and (3) verifying edge cases or error handling for existing logic.
