القائمة
Testing workflow for the machine: characterization tests for legacy code, specification tests for greenfield, and the test-quality checklist. Use when writing tests or measuring coverage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
File a machine self-diagnostic report as a tagged GitHub issue. When a tool, daemon, hook, skill, or agent hangs, errors, returns garbage, or behaves wrong, open a `machine-report`-labeled issue on the machine plugin repo so every plugin user's reports funnel to the maintainer. Requires `gh` logged in. Write-side only — it logs, it does not fix. Trigger: "/report", "report a problem", "this tool is broken", "file a machine report", "log this hang/error/hiccup".
Consume the machine self-diagnostic backlog. Lists the open `machine-report` GitHub issues on the machine repo, ranks them by severity then age, fixes the single highest-priority one at its root cause, verifies green, then closes that issue. The act side of /report (which only writes). Machine-repo-only skill — not shipped to other installs. Trigger: "/resolve", "resolve a report", "triage the reports", "fix the top report", "work the reports backlog".
Second-AI review via the Codex CLI at the drill's single review point — the consolidated review of the finished diff, alongside the persona panel, before a landing is proposed. Advisory only: it returns notes and concerns for the driver and user to weigh, it never gates, blocks, merges, or edits. Skips cleanly when codex is not installed. Trigger via "/codex-review", "codex review", "second opinion from codex", or invoked by the drill skill.
The drill — the orchestrator's default driver mode. Runs grill-first: the drill and the user refine a request one question at a time until the user calls it a valid plan. From there the job runs autonomously — a plan subagent writes a markdown brief, a miner implements it on a git-fs branch inside the orchestrator's worktree, and the gate iterates until the build is green — with one consolidated advisory review (personas + codex) at the end. The drill surfaces only to land the work into main, plus on any blocker it cannot resolve. The live roster lives in the hub (claims + board), not on disk. Trigger via "/drill", "drill mode", "orchestrator mode", "background this", "spawn an agent for this", "drive this".
Promote crystallized brainstorm findings into board tickets. After a brainstorm (drill grill) settles one or more well-scoped features, this turns each into a card on the current cwd's board so the drill's plan step can iterate per ticket. The bridge between brainstorm and plan — it creates tickets, it does not plan or implement. Trigger: "/promote", "promote these", "promote to tickets", "make tickets", "turn findings into cards".
Run the single ongoing chat that resolves the open plan and implementation questions parallel agents raise. Plan/implement agents post questions to mesh and wait; the questioneer aggregates them into one prioritized queue, presents each to you for a decision, and writes the answer back so the waiting agent proceeds. It routes decisions — it does not plan, implement, or dispatch. Trigger: "/questioneer", "questioneer", "answer the questions", "resolve open questions", "what are the agents blocked on".
| name | workflow-testing |
| description | Testing workflow for the machine: characterization tests for legacy code, specification tests for greenfield, and the test-quality checklist. Use when writing tests or measuring coverage. |
| license | Apache-2.0 |
| compatibility | Designed for Claude Code |
| allowed-tools | Read, Write, Edit, Bash(pytest:*), Bash(ruff:*), Bash(npm:*), Bash(npx:*), Bash(node:*), Bash(jest:*), Bash(vitest:*), Bash(go:*), Bash(cargo:*), Bash(mix:*), Bash(uv:*), Bash(bundle:*), Bash(php:*), Bash(phpunit:*), Grep, Glob, mcp__plugin_machine_context7__resolve-library-id, mcp__plugin_machine_context7__query-docs |
| user-invocable | false |
| metadata | {"version":"3.0.0","category":"workflow","status":"active","updated":"2026-06-12","tags":"workflow, testing, ddd, tdd, coverage"} |
| progressive_disclosure | {"enabled":true,"level1_tokens":100} |
| triggers | {"keywords":["testing","characterization tests","coverage","DDD","TDD","behavior preservation","test"],"agents":["manager-ddd","manager-tdd","expert-testing","expert-performance","expert-refactoring"]} |
Specialists own the method: manager-tdd (red-green-refactor),
expert-debug (bugs). Coverage strategy: ref-testing-pyramid.
Quality gate: /gate. This skill is the testing-specific checklist.
| Rationalization | Reality |
|---|---|
| "Already covered by integration tests" | Integration tests catch different bugs than unit tests. |
| "Mocking the DB is too hard, skip it" | Hard-to-test means a missing abstraction boundary. |
| "80% coverage is good enough" | Coverage targets are floors; the missing paths are error handling. |
| "Utility functions don't need tests" | Utilities are the most reused code; a bug propagates everywhere. |
| "Passed locally, CI will pass" | Trust CI output, not local runs. |
| "Flaky tests are normal, re-run" | Fix the flakiness or quarantine the test explicitly. |
skip/t.Skip() without a linked issue.