agentleFS
Sign inStart free
zaxbysaucezaxbysauce/opencode-swarm/.agents/skills/qa-sweep/SKILL.md

qa-sweep

Skill517 starsChanged 3 days agoMITView on GitHub

Codex adapter for independent QA review of opencode-swarm changes. Use after implementation or debugging when the user asks for a QA sweep, regression check, review pass, quality gate, or confidence check before publishing.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Read .claude/skills/qa-sweep/SKILL.md for the source protocol, then translate it to Codex tools.

    line 10
  2. Distinctive:

    Run focused validation commands that match the changed surface.

    line 16

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

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

QA Sweep

Read .claude/skills/qa-sweep/SKILL.md for the source protocol, then translate it to Codex tools.

Codex-specific execution notes:

  • Review the diff first with git status --short and git diff --stat.
  • Inspect changed files directly; do not rely only on summaries.
  • Run focused validation commands that match the changed surface.
  • For code-review output, lead with findings by severity and file/line references.
  • For implementation QA, report residual risks and tests run.

Also load $running-tests when executing tests and $engineering-conventions when invariant-sensitive areas changed.

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.

Check your setup, free