agentleFS
Sign inStart free
MCamnerMCamner/mq-image-analyze/skills/release-readiness/SKILL.md

release-readiness

Skill1 starsChanged 22 days agoMITView on GitHub

Use when preparing mq-image-analyze for release by checking version sync, docs, tests, CLI, MCP tools, model safety, examples, and Git state.

  • Reads credentials

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dependency-cve-sweep, fleet-standard-adoption and 10 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.
  • berntpoppSkill

    dependency-cve-sweep

    Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.

    Also in 12 projects that use this

  • berntpoppSkill

    fleet-standard-adoption

    Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.

    Also in 12 projects that use this

  • IgorGanapolskySkill

    ci-failure-triage

    Triage a CI / PR check failure by READING the failure body before forming any hypothesis. Triggered whenever a required check is red, a PR is BLOCKED, a merge won't land, or you're about to call a failure "transient", "flaky", "stale", or "orphaned". Prevents dismissing a real failure (e.g. real CodeQL security alerts) as noise.

    Also in 14 projects that use this

  • VersoXBTSkill

    code-quality-review

    Perform structured code reviews enforcing quality standards, naming conventions, architecture patterns, and team agreements. Use when the user says 'review this code', 'code review', 'check quality', 'review my PR', 'what's wrong with this', 'improve this code', 'review before merge', 'peer review', or 'audit this'. Also triggers on 'code quality', 'review standards', 'enforce conventions', 'tech debt check', 'lint review', or when user completes a significant code change.

    Also in 12 projects that use this

  • ffsshhttiikkSkill

    unit-testing

    Unit testing best practices and patterns

    Also in 3 projects that use this

  • jarosser06Skill

    test-strategy

    Plans pytest test strategies for Drift's 90%+ coverage requirement using coverage analysis, edge case identification, and test suite design. Use when determining what tests to write, analyzing coverage gaps, or planning test strategies.

    Also in 4 projects that use this

  • +2 more from berntpopp

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 1

    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:

    Use this skill before tagging or publishing mq-image-analyze.

    line 8
  2. Distinctive:

    If a narrower check is enough:

    line 58

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

Release Readiness

Use this skill before tagging or publishing mq-image-analyze.

Evals

Should trigger

  • "is mq-image-analyze ready to release?"
  • "run the release checklist"
  • "check version and changelog alignment"
  • "what's blocking the release?"

Should not trigger

  • "update the docs" → use docs-maintainer
  • "add a CLI flag" → use cli-maintainer
  • "change a model backend" → use model-setup-maintainer

Always Inspect

  • git status --short
  • VERSION
  • pyproject.toml
  • CHANGELOG.md
  • README.md
  • SKILLS.md
  • docs/release.md
  • docs/json-schema.md
  • docs/mcp-tools.md
  • docs/tool-safety.md
  • scripts/validate.sh
  • release-check.sh

Blockers

  • dirty worktree with unrelated changes
  • version mismatch between VERSION, pyproject.toml, README, and changelog
  • failing tests
  • CLI entry point failure
  • tracked model weights or .env
  • docs missing new CLI/MCP/JSON behavior
  • skill status drift
  • output contract changes without schema/tests

Verification

bash scripts/validate.sh
bash release-check.sh

If a narrower check is enough:

python -m compileall mq_image_analyze -q
python -m pytest -q
mq-image --help
mq-image --version

Report Format

Return:

  • status: ready, blocked, or uncertain
  • blockers
  • changed files
  • checks run
  • checks skipped and why
  • model/API credentials not verified, if applicable

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