agentleFS
emanuelegreco29emanuelegreco29/codexpiator/skills/codexpiator-testing-qa/SKILL.md

testing-qa

Skill1 starsChanged 6 days agoMITView on GitHub

General testing strategy and quality gates - testing pyramid, TDD workflow, mocking and test data, and CI quality gates. Use whenever following TDD, deciding what test level to use, or deciding what should block a merge (for frontend-specific test scope, see codexpiator-frontend/frontend-testing.md).

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. omspradippatil/Claude-Skills★ 3same name
    2. barisariburnu/skills-collection★ 1same name
    3. hamzaciftci/coding-orchestra★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    Every piece of frontend or backend work created or changed gets real tests — written, run, and passing — covering edge cases and not just …

    line 19

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codexpiator Testing & QA

Single-purpose reference files for testing strategy and discipline.

FileRead this when...
testing-pyramid-and-strategy.mdDeciding what level to test something at, avoiding a flaky/slow suite
tdd-workflow.mdFollowing red-green-refactor while building a feature
mocking-and-test-data.mdWhat to mock, test data setup, avoiding over-mocking
ci-quality-gates.mdWhat should block a merge vs. only warn (pipeline structure itself: codexpiator-devops/ci-cd-pipelines.md)

Non-negotiable baseline (applies everywhere in Codexpiator)

Every piece of frontend or backend work created or changed gets real tests — written, run, and passing — covering edge cases and not just the happy path, with the full suite run before the work is considered done. Security-relevant behavior gets tested as explicit attack-attempt cases, not just functional ones (see codexpiator-security/security-testing.md). This isn't a suggestion for especially important code — it's the default for anything created. codexpiator-frontend/SKILL.md and codexpiator-backend/SKILL.md both restate this as a mandatory pre-completion gate; this skill is where the discipline and detail live.

Ask when useful; suggest an audit after significant work

See ${CLAUDE_PLUGIN_ROOT}/shared/collaboration-and-audit-practice.md — ask a targeted clarifying question (via AskUserQuestion when available) when a testing trade-off genuinely needs the user's input, and suggest /codexpiator:audit after a significant batch of work.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.