agentleFS
Sign inStart free
juanitourquizajuanitourquiza/shipframe/skills/backend-release/SKILL.md

backend-release

Skill4 starsChanged 21 days agoMITView on GitHub

Verify backend/API releases with tests, migrations, queues, integrations, and endpoint smoke checks.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use for Laravel, Node, Python, Rails, Go, or other backend/API releases.

    line 11
  2. Distinctive:

    Check framework-specific migration/deprecation steps and compatibility windows.

    line 18
  3. Distinctive:

    Run or list exact checks: dependency validation, lint/static analysis, tests, build/compile.

    line 19
  4. Distinctive:

    Check required env/config changes are documented and not committed as secrets.

    line 20
  5. Very specific:

    Run deploy-evidence before declaring completion.

    line 22
  6. Distinctive:

    Never mark complete from a green CI job alone.

    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

Backend Release

Use for Laravel, Node, Python, Rails, Go, or other backend/API releases.

Steps

  1. Load project-profile for app-specific release rules.
  2. Detect framework, package manager, and runtime.
  3. Identify migrations, queues, scheduled jobs, webhooks, and external integrations affected by the diff.
  4. Check framework-specific migration/deprecation steps and compatibility windows; use the project's framework pack when present.
  5. Run or list exact checks: dependency validation, lint/static analysis, tests, build/compile. Optionally run a performance check when the diff changes hot paths, query volume, concurrency, or resource use; record a baseline and avoid unsupported thresholds.
  6. Check required env/config changes are documented and not committed as secrets.
  7. Smoke health endpoints and affected API routes in the intended environment.
  8. Run deploy-evidence before declaring completion.

Never mark complete from a green CI job alone; smoke the intended runtime environment.

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