Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes PHP codebase for test coverage gaps. Detects untested classes, methods, branches, exception paths, and edge cases. Provides actionable recommendations.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Analyzes PHP codebase to identify untested code and coverage gaps.
# Find all PHP classes in src/
Glob: src/**/*.php
# Find all test files
Glob: tests/**/*Test.php
# Compare: class Foo in src/ should have FooTest in tests/
Pattern Matching:
src/Domain/User/User.php → tests/Unit/Domain/User/UserTest.php
src/Application/PlaceOrder/PlaceOrderHandler.php → tests/Unit/Application/PlaceOrder/PlaceOrderHandlerTest.php
// For each public method in class
Grep: "public function [a-z]" --glob "src/**/*.php"
// Check if test method exists
Grep: "test_methodName" --glob "tests/**/*Test.php"
Detection Logic:
Class: Order
├── confirm() → test_confirm_* exists? ✅/❌
├── cancel() → test_cancel_* exists? ✅/❌
├── ship() → test_ship_* exists? ✅/❌
└── addItem() → test_addItem_* / test_add_item_* exists? ✅/❌
If/Else Branches:
// Source code
public function process(Order $order): void
{
if ($order->isPending()) { // Branch 1: pending
$this->processPending($order);
} elseif ($order->isConfirmed()) { // Branch 2: confirmed
$this->processConfirmed($order);
} else { // Branch 3: other
throw new InvalidStateException();
}
}
// Required tests:
// - test_process_when_pending_*
// - test_process_when_confirmed_*
// - test_process_when_other_throws_exception
Switch Statements:
// Source code
match ($status) {
'pending' => $this->handlePending(),
'confirmed' => $this->handleConfirmed(),
'shipped' => $this->handleShipped(),
default => throw new UnexpectedValueException(),
};
// Required tests: one per case + default
// Detect throw statements
Grep: "throw new" --glob "src/**/*.php"
// Each throw should have corresponding test with expectException
Example:
// Source
public function withdraw(Money $amount): void
{
if ($amount->greaterThan($this->balance)) {
throw new InsufficientFundsException(); // Line 15
}
}
// Required test
public function test_withdraw_throws_for_insufficient_funds(): void
{
$this->expectException(InsufficientFundsException::class);
// ...
}
| Type | Values to Test | Detection |
|---|---|---|
| Null | null input | Parameters without type hint or nullable |
| Empty | [], '', 0 | Collection/string/numeric parameters |
| Boundary | min, max, min-1, max+1 | Constants, validation limits |
| Unicode | 'émoji 🎉' | String parameters |
| Concurrent | Race conditions | Shared state, repositories |
Detection Patterns:
// Nullable parameters
Grep: "\?[A-Z]" --glob "src/**/*.php" // ?Type
Grep: "null\|" --glob "src/**/*.php" // Type|null
// Collections
Grep: "array \$" --glob "src/**/*.php"
Grep: "iterable" --glob "src/**/*.php"
// Numeric limits
Grep: "const MAX_" --glob "src/**/*.php"
Grep: "const MIN_" --glob "src/**/*.php"
List all production classes:
Glob: src/**/*.php
List all test classes:
Glob: tests/**/*Test.php
Build mapping:
ProductionClass → [TestClass, TestClass]
For each production class:
covered_classes / total_classes * 100For each public method:
test_{method} patterns in teststested_methods / total_methods * 100For each conditional:
# Test Coverage Analysis Report
## Summary
| Metric | Value | Target |
|--------|-------|--------|
| Class Coverage | 75% | 90% |
| Method Coverage | 60% | 80% |
| Branch Coverage | 45% | 70% |
## Untested Classes
| Class | Location | Priority |
|-------|----------|----------|
| `PaymentProcessor` | src/Domain/Payment/ | High |
| `EmailNotifier` | src/Infrastructure/ | Medium |
## Untested Methods
| Class | Method | Reason |
|-------|--------|--------|
| `Order` | `splitShipment()` | No test found |
| `User` | `resetPassword()` | Only happy path tested |
## Uncovered Branches
| File | Line | Branch | Missing Test |
|------|------|--------|--------------|
| Order.php | 45 | else (cancelled) | test_ship_when_cancelled |
| User.php | 23 | null check | test_with_null_email |
## Missing Edge Cases
| Class | Method | Edge Case |
|-------|--------|-----------|
| `Cart` | `addItem()` | Empty cart, max items |
| `Money` | `add()` | Zero amount, overflow |
## Action Items
### Critical (Must Have)
1. Add `PaymentProcessorTest` — handles money
2. Add `test_order_ship_when_cancelled` — business rule
### High Priority
1. Add null checks for `User::resetPassword()`
2. Add boundary tests for `Cart::addItem()`
### Recommended Skills
| Gap | Skill | Action |
|-----|-------|--------|
| Missing unit test | `acc-create-unit-test` | Generate test class |
| Missing integration test | `acc-create-integration-test` | Generate DB test |
| Need test data | `acc-create-test-builder` | Generate builder |
| Level | Coverage | Action |
|---|---|---|
| Critical | <50% | Immediate attention |
| Warning | 50-70% | Prioritize improvement |
| Good | 70-90% | Monitor and maintain |
| Excellent | >90% | Focus on edge cases |
After analysis, recommend using:
acc-create-unit-test — for missing unit testsacc-create-integration-test — for missing integration testsacc-create-test-builder — for complex test dataacc-create-mock-repository — for repository testsまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
日本語の概要は準備中です。原文の説明を表示しています。
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
日本語の概要は準備中です。原文の説明を表示しています。
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
日本語の概要は準備中です。原文の説明を表示しています。