agentleFS
mejbaurbaharmejbaurbahar/software-tester-skills/AGENTS.md

software-tester-skills

AGENTS.md1 starsChanged 52 days agoMITView on GitHub

Instructions for AI coding agents working in this repository (Claude Code, Codex, Cursor, Gemini CLI, Antigravity and others). All must succeed before you commit. CI runs the same checks. 3. Python scripts are stdlib only and must run on Python 3.9+. Do not add dependencies. 4. install.sh must stay Bash 3.2 compatible (macOS) and must never overwrite files it did not create.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Source of truth is skills/ and commands/: Never hand-edit generated files: README.md marked blocks, adapters/, .claude-plugin/*.json, …

    line 9
  2. Distinctive:

    After changing skills or commands run, in this order:

    line 10
  3. Distinctive:

    All must succeed before you commit.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

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

AGENTS.md

Instructions for AI coding agents working in this repository (Claude Code, Codex, Cursor, Gemini CLI, Antigravity and others).

What this repo is

A library of Agent Skills (skills/<name>/SKILL.md) and slash commands (commands/*.md) for software testing and QA, plus tooling that generates the README catalog, per-tool command adapters and the GitHub Pages site.

Golden rules

  1. Source of truth is skills/ and commands/. Never hand-edit generated files: README.md marked blocks, adapters/**, .claude-plugin/*.json, _site/**.
  2. After changing skills or commands run, in this order:
    python3 scripts/build_adapters.py
    python3 scripts/build_readme.py
    python3 tests/validate_skills.py
    All must succeed before you commit. CI runs the same checks.
  3. Python scripts are stdlib only and must run on Python 3.9+. Do not add dependencies.
  4. install.sh must stay Bash 3.2 compatible (macOS) and must never overwrite files it did not create.

Writing or editing a skill

  • Path: skills/<kebab-case-name>/SKILL.md; the directory name must equal name.
  • Frontmatter (required): name, description, license, and metadata with category (one of the ids in scripts/stsk.py CATEGORIES), version, tags.
  • description is the routing key: start with "Use when …", list concrete triggers and keywords, stay under 1024 characters, no marketing language.
  • Body: a # Title, when to use / not use, a procedure, real copy-paste commands, checklists, pitfalls, and a ## Related line listing other skills in backticks (each must exist).
  • Be specific and correct: real flags, real tool names, no invented APIs. Prefer tables and checklists over prose. Target 60–150 lines; move long material to references/*.md.
  • Security-related skills must state the authorization requirement and keep the guidance defensive.
  • New skills must also be added to the routing table in skills/qa-skill-router/SKILL.md (the validator enforces this).

Writing or editing a command

  • commands/<verb-noun>.md with frontmatter description (≤ 100 chars) and a quoted argument-hint.
  • The body is instructions for the agent, uses $ARGUMENTS, names the skills it uses as Use the `skill-a` and `skill-b` skills. and ends with a concrete output.
  • Regenerate adapters afterwards.

Using these skills in a project (for agents reading this file elsewhere)

For any testing, QA, test-planning or test-review task, first consult skills/qa-skill-router/SKILL.md and load the 1–3 skills it points to. Run security and load tests only against systems the user owns or is authorized to test.

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.