單元測試

Runs a complete phase workflow: audit existing work, fill gaps, run tests, verify acceptance criteria, and report readiness for next phase. Use when user asks to run or complete a project phase.

Defines the project's holistic quality strategy, test policies, and the 'Unified Feedback Protocol'. Establishes the single source of truth for all quality assurance procedures, unifying both automated and human-driven governance.

Write comprehensive test coverage across unit, integration, regression, end-to-end, and manual tests. Watch for deprecation warnings in test output and address them immediately. Use when writing tests, implementing features, or before creating pull requests.

Comprehensive Go testing strategies including table-driven tests, testify assertions, gomock interface mocking, benchmark testing, and CI/CD integration

Gather examples for the acceptance test; use when we are about to start development of a new feature

Reference and maintain documentation of the project's technical stack including frameworks, languages, databases, testing tools, and third-party services. Use this skill when choosing technologies for implementation, adding new dependencies or libraries, setting up project infrastructure, configuring build tools and package managers, integrating third-party services (authentication, email, monitoring), selecting appropriate frameworks for features, ensuring consistency with existing technology choices, documenting technology decisions, reviewing technology compatibility, or onboarding team members to the tech stack. Apply this skill when making technology decisions, adding new tools or services, documenting the stack, or ensuring new code aligns with the project's established technical architecture.

Execute tests following TDD cycle: RED (verify test fails) → GREEN (implement to pass) → REFACTOR.Interprets tests.json and performs steps using available tools (browser MCP, API, CLI, etc.).WHEN TO USE:- Starting implementation of a ticket with TDD: yes- After writing test spec (3-spec.md) and tests.json- When user says "run tests", "test this", "TDD cycle"- After fixing a failing testREQUIRES:- Ticket with 3-spec.md- tests.json in .pmc/docs/tests/tickets/T0000N/

Use when implementing new features. Enforces TDD workflow - write tests FIRST, then implementation. Ensures AAA pattern, proper coverage, and quality test design.

SLASH COMMAND ONLY - Do NOT invoke automatically. Only runs via /test-gh-skills command. Executes Python test orchestrator for 80 tests across 6 skill groups.

SMC trading agent skill for Alpha Harness backtesting. Provides ICT/SMC methodology,decision frameworks, and behavioral guidelines for autonomous trading in simulatedenvironments. USE WHEN agent wakes in harness, needs to analyze markets, decide onsetups, or place orders.

Create new BAP (Bitcoin Attestation Protocol) identities using the bap CLI. Supports Type42 (modern) and Legacy identity formats. Creates encrypted .bep backup files stored in Flow's /.flow/.bsv/backups/ directory.

RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes

Expert React - Hooks, composants, state management, data fetching, testing, styling et patterns modernes

Comprehensive gap analysis framework for identifying missing capabilities, coverage, and requirements. Use for requirements vs implementation gaps, test coverage analysis, documentation gaps, security posture assessment, performance benchmarks, feature parity analysis, team capability gaps, infrastructure coverage, compliance gaps, and accessibility analysis. Includes SWOT, maturity models, and automated gap detection.

PROACTIVE skill - STOP and invoke BEFORE writing dbt SQL. Validates models against coding conventions for staging, integration, and warehouse layers. Covers naming, SQL structure, field conventions, testing, and documentation. CRITICAL - When about to write .sql files in models/, invoke this skill first, write second. Supports project-specific convention overrides and sqlfluff integration.

Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invoke when user mentions "test plan", "QA", "what to test", "testing requirements", or "test scenarios".

AI-powered PR Author Agent that transforms Observability Diff Plans into Pull Requests. Use when: (1) Generating instrumentation code from Scout Agent output, (2) Creating OTel configuration, correlation headers, lineage specs, (3) Scaffolding telemetry validation tests, (4) Creating GitHub/GitLab PRs with observability artifacts. Triggers: "generate PR from diff plan", "create instrumentation PR", "scaffold observability code", "generate OTel config", "create telemetry PR".

Generate actionable, dependency-ordered task lists from implementation plans usingSpecification-Driven Development (SDD) methodology. Use when creating executablework breakdown, task lists, or executing the /tasks command.This skill analyzes design artifacts (plan, contracts, data models, test scenarios)and generates a sequenced task list with parallel execution markers. Tasks followTDD (test-first) and contract-first principles, with clear dependencies and file paths.Triggered by: /tasks command, user request for "task list", "work breakdown","implementation steps", or "what tasks do I need to complete?".

Exploit AWS, Azure, and GCP cloud misconfigurations including S3 buckets, IAM roles, metadata services, serverless functions, and cloud-specific privilege escalation. Use when pentesting cloud environments or assessing cloud security.

Generate comprehensive implementation plans using Specification-Driven Development (SDD)methodology. Use when creating technical design, implementation roadmap, or executingthe /plan command.This skill orchestrates the plan-template.md execution flow, generating research, datamodels, API contracts, and test scenarios. It validates constitutional compliance(Library-First, Test-First, Contract-First) and prepares for task generation.Triggered by: /plan command, user request for "implementation plan", "technical design","how to implement", or "design this feature".