dev-tests
Skill6 starsChanged 20 days agoApache-2.0View on GitHub
Plan risk-based coverage and execute functional acceptance across backend, APIs, pages, UI, business logic and end-to-end journeys. Run existing scoped checks; route source fixes to their owner.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- api-specSkill
- ask-aiSkill
- dev-frontendSkill
- dev-javaSkill
- dev-rustSkill
- dev-typescriptSkill
- domain-modelingSkill
- human-writingSkill
- ops-browserSkill
- ops-clientSkill
- ops-deviceSkill
- product-specSkill
- repo-auditSkill
- repo-deliverySkill
- repo-mapSkill
- repo-reviewSkill
- to-taskSkill
- ui-specSkill
- work-retroSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
When asked to execute functional acceptance, run the reachable authorized cases.
- Distinctive: line 50
Read current project commands and their effects before execution.
- Distinctive: line 81
Read Playwright E2E only for coordinating generated browser-test acceptance.
- Distinctive: line 82
Read coverage when deriving or reconciling the acceptance matrix.
- Distinctive: line 83
Read execution before running checks or making regression claims.
- Distinctive: line 84
Read functional workflow for functional campaigns and resumed case inventories.
- Distinctive: line 85
Read API and logic for network, business status and persistence.
- Distinctive: line 86
Read page walkthrough for real UI journeys and browser evidence.
- Distinctive: line 87
Read test record for functional plans, defects, coverage and recovery.
- Distinctive: line 88
Read roles and performance only for relevant multi-user, authorization or performance requirements.
- Distinctive: line 89
Read result contract when consuming results or returning evidence.
- Distinctive: line 90
Read change preservation when code deletion or instruction changes participate.
- Distinctive: line 91
Read performance measurement for scoped comparative performance acceptance.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dev Tests
Entry Gate
Own a bounded test-coverage and evidence decision for a declared feature, change, or journey. For existing projects, default to deriving and running cases from current code, interfaces and available page observations; a complete PRD is not required. Record conflicts or unverifiable business meanings for later human confirmation, continue independent checks, and withhold only dependent business verdicts or unsafe operations. During product/design work, identify risks, testability gaps and provisional checks without waiting for implementation. Resolve applicable authorities, their acceptance status, target basis, environment and permission before execution; only settled business oracles support business-acceptance verdicts; baseline regression and provisional exploration retain their narrower meaning. Reuse the project test plan and its IDs. When asked to execute functional acceptance, run the reachable authorized cases; a checklist alone does not complete the run.
Route Map
| Request condition | Read | Result |
| AI-generated Playwright journeys or test healing apply | AI E2E acceptance | Frozen cases, bounded authoring handoff and native-runner evidence |
| Design early checks or reconcile risk-based coverage against contracts | coverage | Requirement-to-layer matrix and qualified gaps |
| Run existing checks, rerun failures, or choose regression scope | execution | Reproducible scoped runs and evidence-bound outcomes |
| Execute a functional acceptance campaign or resume its case inventory | functional workflow | Real journeys, correlated results, retest and cleanup |
| API or business-state behavior participates | API and logic | Wire, business status and independent persistence assertions |
| Pages, UI or clicks participate | page walkthrough | Reachability, real interaction and visible outcomes |
| Record functional cases, defects or recovery | test record | Finite coverage, case evidence and recovery queue |
| Deletion, moves/renames, identifiers, enforcement rules or instructions change | change preservation | Original acceptance, positive controls, consumer regressions and qualified comparison |
| Scoped performance acceptance or before/after comparison participates | performance measurement | Comparable metrics, protected journeys and qualified verdicts |
| Role isolation, concurrent users or load scenarios apply | roles and performance | Authorized scenarios, metric interpretation and comparable measurements |
| Compose a result for review or another owner | result contract | Versioned basis, coverage, evidence and handoff |
Invariants
- Derive user-facing copy and feedback type/timing expectations from the original request and accepted Product/UI decisions, not candidate output. Exercise the affected state; distinguish action dispatch from progress/completion. Candidate specs, tests and green counts cannot approve an unsupported presentation change.
- Product behavior belongs to
product-spec, visual behavior toui-spec, and wire semantics toapi-spec. Test ambiguity cannot silently decide those contracts. - Select and run existing project tests within scope. Missing tests, harness changes,
fixtures requiring source edits, and fixes belong to the matching implementation
owner. Browser page/DOM mechanics belong to
ops-browser, desktop-client control toops-client, and mobile device/app lifecycle or native UI toops-device. These names are handoff targets, not automatic invocation or granted capabilities. - Read current project commands and their effects before execution. Use isolated test state and authorized resources; preserve safety stops, denied routes and scope limits. A failure does not authorize another identity, mechanism, or environment to bypass them.
- Preserve
passed,failed,blocked,not-run, andexcludedseparately. A mock, fixture, static check or lower layer proves only its observed boundary, never a real integration or complete E2E. Missing access is a blocker, not an exclusion. - Rebind evidence after requirement, UI, code, configuration or environment changes. Reuse unaffected evidence only with an explicit impact rationale; old green results cannot approve a new basis by default.
- Select raw observations for the actual assertions and estimate output growth before scaling a capture matrix. Follow the test record for evidence sufficiency; storage retention and cleanup remain with the host owner.
- Produce test evidence, not a competing task ledger or a release verdict.
to-taskowns durable work reconciliation,repo-reviewthe fixed-basis review, andrepo-deliveryseparately authorized Git actions. No deployment, installation, publication, production load, or implicit promotion follows from testing. - Consolidate delegated case results into the frozen inventory before selecting more work. An agent terminal state closes only its assigned execution, not another evidence layer or the run verdict.
Output Map
Return the result contract: frozen basis and authority versions, layer matrix, executed checks and evidence, failures and blockers, justified exclusions, remaining acceptance gaps and smallest owner-specific next action. State whether a first real E2E was observed and its exact boundary. Never flatten the matrix into “all tests passed” when required cells remain unresolved.
Reference Map
- Read Playwright E2E only for coordinating generated browser-test acceptance.
- Read coverage when deriving or reconciling the acceptance matrix.
- Read execution before running checks or making regression claims.
- Read functional workflow for functional campaigns and resumed case inventories.
- Read API and logic for network, business status and persistence.
- Read page walkthrough for real UI journeys and browser evidence.
- Read test record for functional plans, defects, coverage and recovery.
- Read roles and performance only for relevant multi-user, authorization or performance requirements.
- Read result contract when consuming results or returning evidence.
- Read change preservation when code deletion or instruction changes participate.
- Read performance measurement for scoped comparative performance acceptance.
- Maintainers only: read eval cases; do not load it during ordinary execution.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

