agentleFS
dceoydceoy/mt5api/.agents/skills/local-qa/SKILL.md

local-qa

Skill7 starsChanged 8 days agoMITView on GitHub

Run local QA including formatting, linting, and testing for the repository. Use whenever any file has been updated.

  • Installs packages

5 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 2

    1. dceoy/ai-coding-agent-skills★ 414% same
    2. dceoy/oracle-pr-loop★ 114% same

    Wrote their own version · 3

    1. talayash/agentrium★ 48same name
    2. dceoy/docker-claude-code★ 2same name
    3. dceoy/gha-for-devops★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Run scripts/qa.sh relative to this skill's directory, not the shell's current working directory.

    line 8
  2. Distinctive:

    After the run, summarize the outcome: success or failure, major warnings, and any files modified.

    line 10
  3. Distinctive:

    Run only commands needed for QA, fixes, and tool installation.

    line 17

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

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

Local QA (format, lint, and test)

Run scripts/qa.sh relative to this skill's directory, not the shell's current working directory. The script changes to the repository root itself. It formats and fixes files in place, so check git status afterward.

After the run, summarize the outcome: success or failure, major warnings, and any files modified.

When something fails

  • Missing tooling (command not found or equivalent): install the tool, preferring the project's package manager (uv, pnpm), then a system package manager, then a language-specific installer (pipx, npm, go install). Rerun scripts/qa.sh and repeat until QA completes. If installation fails or needs privileges you lack, report what was attempted and the exact failure, then stop.
  • Any other failure: fix the root cause and rerun until QA passes or you hit a blocker. Do not bypass or weaken checks, because the script is the repository's quality gate.

Run only commands needed for QA, fixes, and tool installation.

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.