원클릭으로 Manus에서 모든 스킬 실행

test-domain

스타27

포크5

업데이트2026년 5월 20일 22:48

Generate or run tests for a specific domain. Use when the user asks to "generate tests", "run tests for domain", "unit test", "integration test", "pytest run", "write test code", or wants to create or run tests for a specific domain.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nrjdalal

nrjdalal/awesome-templates

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Domain Test Generation/Execution

Target: $ARGUMENTS (domain name + "generate" or "run")

Default Flow Position

Step: verify (canonical owner). run mode is the standard post-implement action.
generate mode itself is an implement-style action; resulting tests must be exercised with run afterward.
Routes after: /review-architecture {name} (self-review) if layer interactions changed → /review-pr (completion gate)
Recursion guard: n/a (verify-step skill, not a planning step)

Procedure Overview

Determine mode — generate or run (ask if unclear)
Generate mode — identify Service/UseCase methods, check existing tests, generate missing files
Run mode — execute pytest with appropriate scope, analyze failures
Verification — verify imports, run tests, run pre-commit

Read docs/ai/shared/skills/test-domain.md for detailed steps and required test file list. Also refer to docs/ai/shared/test-patterns.md for factory patterns and test examples.

이 저장소의 다른 Skills

같은 저장소

sync-guidelines

nrjdalal/awesome-templates

Inspect drift between code, shared workflow references, and Claude, Codex, or Antigravity harness assets after architecture or workflow changes.

2026-07-1427

sync-guidelines

nrjdalal/awesome-templates

This skill should be used when the user asks to "sync guidelines", "document inspection", "check skill updates", "update project-dna", "sync patterns", "verify code-document consistency", or after architecture changes to verify Skills/AGENTS.md/CLAUDE.md match the actual code.

2026-07-1427

plan-feature

nrjdalal/awesome-templates

Guide a feature from requirements interview through architecture analysis, security check, and task decomposition.

2026-07-0927

plan-feature

nrjdalal/awesome-templates

This skill should be used when the user asks to "plan feature", "design feature", or wants to plan and design a new feature before implementation.

2026-07-0927

review-architecture

nrjdalal/awesome-templates

Audit a domain or the full repository for architecture compliance using the shared architecture checklist and repository rules.

2026-07-0427

review-pr

nrjdalal/awesome-templates

Review a pull request or local diff against the repository's shared Review Protocol (correctness, regression, stability, contract, architecture, security, governance).

2026-07-0427

name	test-domain
argument-hint	domain_name generate\|run
description	Generate or run tests for a specific domain. Use when the user asks to "generate tests", "run tests for domain", "unit test", "integration test", "pytest run", "write test code", or wants to create or run tests for a specific domain.

Domain Test Generation/Execution

Target: $ARGUMENTS (domain name + "generate" or "run")

Default Flow Position

Step: verify (canonical owner). run mode is the standard post-implement action.
generate mode itself is an implement-style action; resulting tests must be exercised with run afterward.
Routes after: /review-architecture {name} (self-review) if layer interactions changed → /review-pr (completion gate)
Recursion guard: n/a (verify-step skill, not a planning step)

Procedure Overview

Determine mode — generate or run (ask if unclear)
Generate mode — identify Service/UseCase methods, check existing tests, generate missing files
Run mode — execute pytest with appropriate scope, analyze failures
Verification — verify imports, run tests, run pre-commit

Read docs/ai/shared/skills/test-domain.md for detailed steps and required test file list. Also refer to docs/ai/shared/test-patterns.md for factory patterns and test examples.