본문으로 건너뛰기
cccskills
무료GitHub에 공개

test-strategy

Plans risk-based test coverage for a feature, service, release, or system by mapping user and business risk to test levels, environments, data, failure paths, automation, exploratory checks, and release gates. Use when choosing what to test or how much evidence is enough. Not for writing one test case, applying TDD to a single behavior, or debugging a failing test.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode
설치 방법 보기

포함된 파일(3)

  • SKILL.md2.6 KB
  • references/risk-matrix.md470 B
  • references/specialized-modes.md1.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Test Strategy

Coverage is a means; risk and failure detection are the decision criteria.

Strategy loop

  1. Identify critical user journeys, assets, contracts, dependencies, and recent change areas.
  2. Score impact and likelihood; include data loss, privacy, money, access, safety, operational, and reputation failure modes.
  3. Map each high-risk item to the cheapest test level that reaches the real failure: unit, contract, integration, component, browser, load, security, exploratory, or production monitoring.
  4. Define fixtures, environment parity, deterministic data, test ownership, test oracle, and cleanup.
  5. Set release gates and explicit exclusions. Include negative, boundary, retry, concurrency, migration, accessibility, and recovery paths when risk warrants them.
  6. Reassess after incidents, architecture changes, dependency changes, and high-churn releases.

Choose specialized test modes

  • Use exploratory charters when risks or failure shapes are not understood; time-box the session, record observations, then convert repeatable discoveries into automated checks.
  • Use contract tests at independently deployed consumer/provider seams; verify compatibility before deployment rather than duplicating implementation tests on both sides.
  • Classify flaky tests by product race, test race, data, environment, dependency, resource contention, or selector drift. Quarantine only with an owner, evidence, expiry, and a still-visible signal; retries are not a fix.
  • Use production tests only with non-destructive synthetic identities, blast-radius controls, monitoring, cleanup, and a tested abort path.
  • Use agent evaluation for stochastic model-backed behavior; ordinary pass rates and snapshots do not capture variance, tool trajectory, cost, or grounding.

Read risk-matrix.md and specialized-modes.md. Avoid a universal coverage percentage, brittle snapshots with no oracle, and tests that pass only because they mock the behavior under test.

Completion condition

The strategy connects risk to an executable check, names ownership and test data, defines release gates, and makes untested risk visible.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

agent-evaluation

무료

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

api-and-interface-design

무료

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

architecture-review

무료

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

behavior-validation

무료

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

branch-integration

무료

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

browser-testing

무료

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

thiientv의 스킬 모두 보기

이 스킬의 문제 신고