agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-release-audit/SKILL.md

metagit-release-audit

Skill4 starsChanged 12 days agoMITView on GitHub

Mandatory before calling work complete when the session changed repo files. Runs format, lint, tests, integration tests, context-aware pip-audit/bandit, and optional gitleaks via task qa:prepush. Use before push, release, or hand-off.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill whenever your session added or edited tracked files in this repository and you are about to hand off or say the task is …

    line 8
  2. Distinctive:

    Run the pre-push quality gate.

    line 12
  3. Distinctive:

    Do not claim readiness unless checks are actually green.

    line 33

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

Auditing Release Readiness

Use this skill whenever your session added or edited tracked files in this repository and you are about to hand off or say the task is done—not only “release” workflows. Read-only Q&A with no writes can skip it.

Workflow

  1. Run the pre-push quality gate.
  2. Capture failing stage logs and iterate fixes.
  3. Re-run until all required checks pass.
  4. Return a short readiness summary.

Commands

  • task qa:prepush
  • task qa:prepush:loop -- 3 (optional bounded retry loop)

Output Contract

Return:

  • pass/fail status by stage (including security_sync / security_audit / security_bandit when triggered)
  • unresolved blockers (if any)
  • push readiness recommendation

Security in the gate is context-aware: lockfile changes run uv sync --frozen --all-extras + pip-audit + bandit; src/ changes run pip-audit + bandit; docs-only diffs skip security. Use task security:scan for a full manual run.

Safety

  • Do not claim readiness unless checks are actually green.

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