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

시작하기

team-add-tests

스타2

포크2

업데이트2026년 2월 27일 02:22

Add critical test coverage — tests ONLY for functionality that could cause production disasters

설치

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

Manus에서 실행

출처

bryanweaver

bryanweaver/claude-agent-kit

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

다운로드

Manus에서 실행

Add Tests — Critical Test Coverage

Add tests for CRITICAL functionality only. Test the 20% that prevents 80% of disasters.

Area to cover: $ARGUMENTS

Execution

With Agent Teams (recommended)

Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

Create a team and spawn teammates:

Create team named add-tests-<area-slug>
Spawn teammates: shipper, reviewer, full-stack-developer, database-admin (if data layer), documentor

Create the following task list with dependencies:

#	Task	Owner	Blocked By
1	Create branch `test/critical-coverage-<area>` from main	shipper	—
2	Identify CRITICAL untested code paths	reviewer	1
3	Write minimal tests for critical application paths	full-stack-developer	2
4	Write minimal tests for critical data integrity paths (if needed)	database-admin	2
5	Run full test suite including new tests	shipper	3, 4
6	Update documentation for new test coverage	documentor	5
7	Commit and create PR to main	shipper	5, 6

Critical = code that could:

Break authentication or authorization
Lose or corrupt user data
Break payments or money flow
Cause a production outage

Skip tests for:

UI formatting and styling
Nice-to-have features
Edge cases that won't impact production
Anything that can be quickly fixed if it breaks

Parallelism: Tasks 3 and 4 can run simultaneously.

Without Agent Teams (fallback)

Execute sequentially using the Task tool:

Task(shipper, "Create branch test/critical-coverage-<area> from main")
Task(reviewer, "Identify CRITICAL untested code in $ARGUMENTS — focus on auth, data integrity, payments, outage risks")
Task(full-stack-developer, "Write minimal tests for critical paths: <reviewer findings>")
Task(database-admin, "Write data integrity tests: <reviewer findings>") — only if needed
Task(shipper, "Run full test suite including new tests")
Task(documentor, "Update docs to reflect new test coverage for: $ARGUMENTS")
Task(shipper, "Commit and create PR: test: add critical coverage for <area>")

Workflow Diagram

┌─────────┐     ┌──────────┐     ┌──────────────────┐     ┌─────────┐     ┌────────────┐     ┌─────────┐
│ Shipper │────►│ Reviewer │────►│ Full Stack Dev   │────►│ Shipper │────►│ Documentor │────►│ Shipper │
│ Branch  │     │ Identify │     │ + DB Admin (||)  │     │Run Tests│     │ Update Docs│     │Commit+PR│
└─────────┘     │ Critical │     │ Write Tests      │     └─────────┘     └────────────┘     └─────────┘
                │ Gaps     │     └──────────────────┘
                └──────────┘

Philosophy

This is a time-boxed effort. Spend hours, not days. The goal is not comprehensive coverage — it's protecting against disasters. Write the minimum tests that prevent the maximum damage.

이 저장소의 다른 Skills

같은 저장소

team-ship

bryanweaver/claude-agent-kit

Build and deploy features — branch, implement, commit, review, test, deploy, PR/merge

2026-06-162

shadcn-components

bryanweaver/claude-agent-kit

shadcn/ui component patterns including Radix UI primitives, CVA variants, form components with React Hook Form, and Tailwind CSS styling. Use when creating UI components, building forms, implementing design systems, or working with shadcn/ui.

2026-02-272

team-all-tools

bryanweaver/claude-agent-kit

List all available tools with their signatures and purposes

2026-02-272

team-audit

bryanweaver/claude-agent-kit

Analyze Claude Code audit logs — session summaries, metrics, timelines, anomaly detection, and claim verification

2026-02-272

team-cleanup

bryanweaver/claude-agent-kit

Technical debt and refactoring — analyze, refactor, and validate code improvements

2026-02-272

team-create-agent

bryanweaver/claude-agent-kit

Create a new custom agent using the meta-agent with guided requirements gathering

2026-02-272

name	team-add-tests
description	Add critical test coverage — tests ONLY for functionality that could cause production disasters
argument-hint	<area or module to add tests for>
disable-model-invocation	true
allowed-tools	Bash(git *), TaskCreate, TaskUpdate, TaskList, TaskGet

Add Tests — Critical Test Coverage

Add tests for CRITICAL functionality only. Test the 20% that prevents 80% of disasters.

Area to cover: $ARGUMENTS

Execution

With Agent Teams (recommended)

Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

Create a team and spawn teammates:

Create team named add-tests-<area-slug>
Spawn teammates: shipper, reviewer, full-stack-developer, database-admin (if data layer), documentor

Create the following task list with dependencies:

#	Task	Owner	Blocked By
1	Create branch `test/critical-coverage-<area>` from main	shipper	—
2	Identify CRITICAL untested code paths	reviewer	1
3	Write minimal tests for critical application paths	full-stack-developer	2
4	Write minimal tests for critical data integrity paths (if needed)	database-admin	2
5	Run full test suite including new tests	shipper	3, 4
6	Update documentation for new test coverage	documentor	5
7	Commit and create PR to main	shipper	5, 6

Critical = code that could:

Break authentication or authorization
Lose or corrupt user data
Break payments or money flow
Cause a production outage

Skip tests for:

UI formatting and styling
Nice-to-have features
Edge cases that won't impact production
Anything that can be quickly fixed if it breaks

Parallelism: Tasks 3 and 4 can run simultaneously.

Without Agent Teams (fallback)

Execute sequentially using the Task tool:

Task(shipper, "Create branch test/critical-coverage-<area> from main")
Task(reviewer, "Identify CRITICAL untested code in $ARGUMENTS — focus on auth, data integrity, payments, outage risks")
Task(full-stack-developer, "Write minimal tests for critical paths: <reviewer findings>")
Task(database-admin, "Write data integrity tests: <reviewer findings>") — only if needed
Task(shipper, "Run full test suite including new tests")
Task(documentor, "Update docs to reflect new test coverage for: $ARGUMENTS")
Task(shipper, "Commit and create PR: test: add critical coverage for <area>")

Workflow Diagram

┌─────────┐     ┌──────────┐     ┌──────────────────┐     ┌─────────┐     ┌────────────┐     ┌─────────┐
│ Shipper │────►│ Reviewer │────►│ Full Stack Dev   │────►│ Shipper │────►│ Documentor │────►│ Shipper │
│ Branch  │     │ Identify │     │ + DB Admin (||)  │     │Run Tests│     │ Update Docs│     │Commit+PR│
└─────────┘     │ Critical │     │ Write Tests      │     └─────────┘     └────────────┘     └─────────┘
                │ Gaps     │     └──────────────────┘
                └──────────┘

Philosophy

This is a time-boxed effort. Spend hours, not days. The goal is not comprehensive coverage — it's protecting against disasters. Write the minimum tests that prevent the maximum damage.