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

project-release

Skill4 starsChanged 21 days agoMITView on GitHub

Orchestrate a generic release by loading project profile rules, running checks, and collecting deploy evidence.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run project-profile to load repo-specific rules.

    line 15
  2. Very specific:

    Run release-checklist to define release gates.

    line 16
  3. Very specific:

    Run deploy-evidence after deploy/publication.

    line 23
  4. Distinctive:

    Do not say "done", "deployed", or "released" unless the final report includes concrete evidence for the intended environment.

    line 28

“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

Project Release

Project Release is the generic ShipFrame release entrypoint. It must work across projects without hardcoding a specific client or product.

Flow

  1. Run project-profile to load repo-specific rules.
  2. Run release-checklist to define release gates. Include migration/deprecation compatibility and rollback planning where relevant. Add a performance verification step only when the change affects measurable runtime/resource behavior; it is optional, not a universal release blocker.
  3. Dispatch by target:
    • frontend/static/UI changes → frontend-release
    • backend/API/jobs/integrations → backend-release
    • both → run both in dependency order from the project profile
    • docs/library-only → run the relevant checklist and evidence steps
  4. Run deploy-evidence after deploy/publication.
  5. Report final status with completed checks, evidence, gaps, and rollback notes.

Completion rule

Do not say "done", "deployed", or "released" unless the final report includes concrete evidence for the intended environment.

Final report

## Project Release Report

**Target:** <target>
**Environment:** <environment>
**Version/tag/commit:** <value>

### Completed
- ✅ <item>

### Evidence
- ✅ <item>

### Gaps / follow-up
- <item or "None">

### Verdict
<Released | Not released | Partially verified>

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