- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
godot-test
by Chen19007
Run GUT unit tests for Godot projects. Use when: (1) Running unit tests, (2) Verifying code changes, (3) TDD development, (4) CI/CD testing.
validating-changes
by squirrel289
"Validate code changes before PR update and merge. Use when preparing to update a PR, pushing changes, or running pre-merge checks: (1) run local CI parity tests, (2) add regression tests for new failures, (3) verify all tests pass before pushing or requesting review."
vertex-ai
by cgk-platform
Test and use Google Vertex AI for video/image generation as an alternative
test-driven-development
by carvalab
TDD workflow guide. Use PROACTIVELY when writing new features or fixing bugs. Enforces Red-Green-Refactor cycle and prevents testing anti-patterns.
subagent-driven-development
by Jackiexiao
(中文)Use when executing implementation plans with independent tasks in the current session
aegis
by ghosty21888
Contract-driven, design-first quality guardrails for AI-assisted full-stack development. Prevents project chaos at scale by enforcing a five-layer protection system: Design → Contract → Implementation → Verification → PM. Use when: starting a new full-stack project, planning a non-trivial feature, dispatching frontend/backend work to coding agents, coordinating multi-agent parallel development, setting up contract tests, or running integration/E2E verification. Triggers on: "aegis init", "design brief", "write contract", "contract test", "integration test", "aegis verify", "multi-agent coordination", "quality guardrails", "project setup with aegis".
mock-skill
by maxoreric
Mock
sdd-system-design
by franztrierweiler
Produit les documents de conception technique (architecture, déploiement,
typography
by rhino-labs
Apply professional typography principles when generating documents, web pages, presentations, or any formatted text output. Use this skill when creating or reviewing HTML/CSS, print documents, resumes, letters, reports, slide decks, emails, or any content where typographic quality matters. Also use when the user asks about font choices, text formatting, spacing, layout, or typographic best practices.
typescript-test-review
by bromanko
This skill should be used when the user asks for "test review", "test coverage", "improve TypeScript tests", "review tests", "test quality", "testing audit", or wants analysis of TypeScript test suites for coverage gaps, edge cases, and testing best practices.
version-skill
by maxoreric
Skill 版本管理的 Skill。当需要 A/B test、切换版本、回滚时触发。触发词:版本、version、A/B test、切换、回滚、promote。
hydromind-ai-advisor
by arun25hyd
Expert hydraulic systems Q&A advisor for the HydroMind AI platform. Use this skill ALWAYS when a user asks ANY question about hydraulic systems, offshore or mobile cranes, HPUs, hydraulic pumps, motors, directional control valves, fault diagnosis, pressure settings, flow calculations, component identification, maintenance procedures, or troubleshooting. Trigger for ANY hydraulic-related query — even general ones like "why is my winch slow" or "what is case drain pressure" or "how do I adjust a pressure relief valve". This skill governs the full Q&A answer workflow: (1) Search internal knowledge base first, (2) web search only if not found in KB, (3) always correct user command errors silently and provide structured answers. Also triggers for NEW SYSTEM DESIGN requests — runs a full interactive intake Q&A, confirms a design plan, then executes 12-step structured design including pump/motor/DCV sizing, filter/tank/pipe sizing, BOM generation, and cooler sizing.
tech-plan-assessment
by qa-pro
对后端技术团队提供的技术方案进行多视角评分与质量评估。支持 PDF、Markdown 和飞书文档格式,从产品、后端、前端、测试四个视角逐项打分,输出总分、各视角得分、问题列表、改进建议和完整评估报告。
spec-to-code-compliance
by aleister1102
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.
context-gathering
by BaxterCooper
Use when entering an unfamiliar codebase, starting a new feature, or before any implementation task. Provides structured exploration protocol to understand before acting.
feature-orchestration
by vineethsoma
Story orchestration with progress tracking, standardized directory structure, and validation
bf-lead-review
by khaki4
Discourse 패턴으로 다관점 리뷰를 수행한다. Tech Spec 리뷰와 에픽 통합 코드 리뷰를 모두 처리하며, 쟁점 해소 프로토콜에 따라 합의/미합의를 분리한다.
riley-prd-gauntlet
by riley-cole
End-to-end PRD workflow from product concept through finalized, cross-validated build spec. Twelve phases — intake, define, grill-me interview, stress test, product vision brief, strategic council, component map, user stories, PRD draft, adversarial review, system validation, finalize and distribute. Supports optional deep research (competitive landscape, internal ticket mining) during intake. Project-agnostic methodology with project-specific config files for precision execution. Use when starting a new PRD, running an adversarial review, validating cross-PRD consistency, researching a product landscape, stress-testing a concept, or running a strategic council review. Trigger on: "PRD gauntlet", "riley-prd-gauntlet", "new PRD", "adversarial review", "cross-PRD validation", "stress test", "strategic council", "research", or "finalize the PRD."
zoho-books
by xHUNx
Zoho Books integration skill (WIP). OAuth setup + API client scaffolding with full module coverage planned.
effect-vitest
by tstelzer
Testing Effect programs with vitest. Use when writing tests for effect-based code.
spec
by robdmc
"Universal artifact specification skill that interviews users to produce well-defined specification documents. Covers any artifact type — software, presentations, analyses, AI skills, threat models, curricula, etc. Invoke as '/spec filename' or '/spec filename hint'. Other skills can delegate specification work by passing a hint string after the filename. Use when the user wants to spec out, define, or plan any artifact before building it."
testing-guidelines
by dcramer
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
spec-generator
by pm-minji
"츠루"로 호출. 새로운 기능의 기획 문서(requirements, design, tasks)를 생성합니다.
documentation
by hk-vk
Documentation documentation and resources. Use this skill when working with Documentation or when the user mentions documentation.