agentleFS
Sign inStart free
willcoliveirawillcoliveira/qualiow-exploratory-testing-skills/.claude/skills/qa-explore-cleanup/SKILL.md

qa-explore-cleanup

Skill15 starsChanged 17 days agoMITView on GitHub

Manage exploratory testing sessions — list, archive, or delete old sessions. Use when user says: "cleanup sessions", "delete old sessions", "archive", "list sessions".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER auto-delete — always show and confirm

    line 72

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

Session Cleanup & Management

This skill is a thin wrapper around qualiow session. Run it in this context — never hand the delete paths to anything that cannot stop and ask.

Session directories follow output/sessions/<YYYY-MM-DD-HHmm>-<kind>-<slug>/ (${CLAUDE_SKILL_DIR}/../qa-explore/references/paths.md, which also resolves the qualiow prefix — write it literally). Archives are still CONFIDENTIAL (${CLAUDE_SKILL_DIR}/../qa-explore/references/security-rules.md): keep them under output/, never upload them. What a complete session directory contains — and which files must survive an archive — is defined in ${CLAUDE_SKILL_DIR}/../qa-explore/references/output-contract.md.

Commands

List Sessions

qualiow session list

Prints every row of output/sessions/INDEX.md and flags directories present on disk but missing from the index as unindexed. Show the output as it comes.

Archive Session

qualiow session archive <session-dir>

Writes output/sessions/<session-dir>.tar.gz. Add --remove to drop the original directory afterwards and mark its index row archived — offer that, don't assume it.

Delete Session

Always confirm with the user before deleting. The command is a dry run until --yes:

qualiow session delete <session-dir>

Show its output — file count, size, and the index rows that would go — then ask the user whether to proceed. Only on an explicit yes:

qualiow session delete <session-dir> --yes

That removes the directory, its row from output/sessions/INDEX.md and its rows from output/bugs/all-bugs.md.

Delete Old Sessions

Same two steps, by age:

qualiow session prune --older-than <days>

Show the list of sessions it would remove, ask, then run it again with --yes.

Rules

  • NEVER auto-delete — always show and confirm
  • Suggest archiving before deleting
  • Remind the user of the 90-day retention default from the security policy when listing sessions older than that

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