agentleFS
Sign inStart free
patronus-protectpatronus-protect/patronus-security-cli/.claude/skills/qa-integrations/SKILL.md

qa-integrations

Skill2 starsChanged 2 months agoApache-2.0View on GitHub

Check that Patronus integrations work — host CLI drift against release pins, plugin manifests, local runtime, hosted API and MCP, OpenAPI contract and marketplace installs in a sandbox. Use as part of the QA run.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run node qa/integrations.mjs.

    line 8
  2. Very specific:

    Host drift: if a host CLI is newer than its pin, the hook QA (node qa/hooks.mjs) already ran against the installed version in the same run.

    line 14
  3. Very specific:

    If its host suite passed, propose a draft PR that bumps the pin in .github/release-host-versions.env.

    line 15
  4. Distinctive:

    If it failed, the existing hook finding explains why.

    line 16
  5. Distinctive:

    Marketplace install, isolated: verify that a new user can install the plugin from the marketplace without touching this machine's real …

    line 18
  6. Very specific:

    Codex: use a temporary CODEX_HOME and HOME in the same way, with patronus-security-scanner integration codex install.

    line 20
  7. Distinctive:

    Never: run install, enable or update against the real home directories.

    line 21
  8. Very specific:

    Hosted API plugin: run npm ci --ignore-scripts && npx playwright test in plugins/codex-api/ if its dependencies are present.

    line 22
  9. Very specific:

    Write any extra findings into ~/.patronus-qa/runs/<date>/integrations.json (append to its findings, keeping the report shape).

    line 24

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

Integration QA

  1. Run node qa/integrations.mjs. It is read-only and checks:
    • the host CLI versions against .github/release-host-versions.env,
    • the plugin manifest versions,
    • the runtime probe and integration <host> status,
    • the published OpenAPI version against contract/openapi-version.json,
    • the hosted MCP tools/list for the QA account.
  2. Host drift: if a host CLI is newer than its pin, the hook QA (node qa/hooks.mjs) already ran against the installed version in the same run.
    • If its host suite passed, propose a draft PR that bumps the pin in .github/release-host-versions.env.
    • If it failed, the existing hook finding explains why. Name both findings together.
  3. OpenAPI drift: diff the published openapi.json against contract/ fixtures and the SDK request/response types. List new or changed endpoints and fields in the finding. A contract update is a draft-PR candidate only when it is mechanical; otherwise propose an issue.
  4. Marketplace install, isolated: verify that a new user can install the plugin from the marketplace without touching this machine's real config.
    • Claude: CLAUDE_CONFIG_DIR=$(mktemp -d) claude plugin marketplace add <repo> then claude plugin install patronus-security@patronus-local (both in the same temporary config dir). Check claude plugin list --json, then delete the directory.
    • Codex: use a temporary CODEX_HOME and HOME in the same way, with patronus-security-scanner integration codex install.
    • Never run install, enable or update against the real home directories.
  5. Hosted API plugin: run npm ci --ignore-scripts && npx playwright test in plugins/codex-api/ if its dependencies are present. Otherwise note that it was skipped.

Write any extra findings into ~/.patronus-qa/runs/<date>/integrations.json (append to its findings, keeping the report shape).

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