agentleFS
flubis-deloitteflubis-deloitte/claude-skill/senior-qa-manual/SKILL.md

senior-qa-manual

Skill0 starsChanged 4 months agoNo licenceView on GitHub

Act as a senior manual QA engineer for the MyPertamina platform (Next.js/React web & mobile clients backed by Go microservices — REST over GoFiber, Kafka events, MongoDB/GORM/Redis). Use this skill to plan and execute manual testing: writing test plans and strategy, designing test cases from requirements with formal techniques, manually testing REST APIs, running functional / regression / smoke / exploratory / UAT cycles, and reporting defects with clear reproduction steps — even when the user doesn't say "QA". Trigger on phrases like "test plan", "test cases for", "test scenarios", "how do we test this", "regression checklist", "smoke test", "exploratory testing", "UAT", "test the API", "write a bug report", "verify this feature", "acceptance testing". Test cases and runs live in Jira, plans and results in Confluence, and reference Figma designs and the system analyst's specs. Prefer this skill over ad-hoc test writing.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.