agentleFS
Sign inStart free
grooownowgrooownow/qa-pilot/skills/project-audit/SKILL.md

project-audit

Skill6 starsChanged 15 days agoLicence not identifiedView on GitHub

Whole-project QA audit — the big picture a per-task check cannot give. Assesses the maturity of the project's "test framework" (layers, CI gates, mocking, test data, selectors, flaky handling, linting), confirms the 3–7 critical user flows with the owner, runs spec-audit at depth "critical" on each chosen flow (entity cards of must-check web patterns: modify vs delete, double submit, silent mutations, UI-only permissions…), samples the test code around those flows, and writes one prioritized roadmap — framework fixes, Must tests per flow, questions, highlights — plus an English action list an agent can execute. Use when entering a project, for an interim audit, or after a large feature or many small changes ("аудит проекта", "общая картина по тестам", "что у нас с тестами в целом", "project QA audit", "health check of QA"). Costs ~250k tokens per flow; the owner picks the flows. Not for a single feature (use qa-pilot:spec-audit) or a single task (use qa-pilot:task-qa).

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use merge-prep, repo-intake and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sd0xdevSkill

    merge-prep

    Pre-merge analysis and preparation. Analyzes source branch vs target branch: commit stats, conflict detection, file impact. Analysis-only v1 — outputs report + suggested commands, does not auto-merge. Use when: user says 'merge prep', 'pre-merge', 'merge analysis', or /merge-prep

    Also in 3 projects that use this

  • AuroraBackcountrySkill

    repo-intake

    Get a picked-up repo ready to work in. Unfamiliar repo: ask intent, map it by reading, write the canonical AGENTS.md, wire the vault, propose a first task. Already-documented repo with no vault space: wire-only — connect it and leave the docs alone. Use when picking up a codebase: "onboard me", "get me set up on this repo", "I cloned/forked this", "map this repo", "wire this into the vault" — or proactively when a repo has no AGENTS.md/CLAUDE.md and real work starts. Check ownership first: on a repo the user doesn't own, intake is vault-first and writes nothing into tracked files. NOT memory refresh (that's memory-checkpoint) or greenfield scaffolding (/scaffold); documented AND wired = nothing to do.

    Also in 3 projects that use this

  • sd0xdevSkill

    issue-analyze

    GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + verdict assessment + investigation strategy.

    Also in 3 projects that use this

  • apacheSkill

    precommit

    Validate and fix Pinot pre-commit checks on affected modules before a commit or PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 13 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.

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