agentleFS
Sign inStart free
nwiizonwiizo/ccswarm/.agents/skills/deploy-workflow/SKILL.md

deploy-workflow

Skill156 starsChanged 8 days agoMITView on GitHub

Release deployment process for ccswarm. Version update, quality gates, build, tag, publish.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. simstudioai/skills★ 2same name
    2. bas1l/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    When release publication is authorized, verify the branch, remote, diff, and unused tag.

    line 31
  2. Distinctive:

    Do not run a second manual publish command alongside the workflow.

    line 41

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

Deploy a new ccswarm release using .github/workflows/release.yml. The workspace has one published crate, crates/ccswarm. Follow the scope in docs/ROADMAP.md and the version-specific notes in docs/releases/.

Pre-Deployment

# Update crates/ccswarm/Cargo.toml and its Cargo.lock package version.
# Update CHANGELOG.md and docs/releases/v<VERSION>.md.

# Quality gates
cargo fmt --all
cargo clippy --workspace --locked -- -D warnings
cargo test --workspace --locked
cargo audit
cargo doc --no-deps --workspace --locked
cargo build --release --workspace --locked
cargo publish -p ccswarm --dry-run --locked
actionlint .github/workflows/release.yml
# Browser example (installs its locked dependencies and Chromium if needed)
CCSWARM_BIN=target/release/ccswarm examples/e2e-playwright/run.sh

Build & Release

When release publication is authorized, verify the branch, remote, diff, and unused tag. Commit and push the reviewed release preparation. Run the Release workflow manually on that exact commit and verify all four native archive builds, smoke tests, and quality checks. Manual runs do not publish.

Then create and push the annotated version tag on the verified commit. The tag workflow rebuilds and validates, creates a complete draft, verifies its downloaded assets, attests the archives, publishes the stable crate, and publishes the GitHub release. Prerelease tags do not publish a crate.

Do not run a second manual publish command alongside the workflow. Verify the completed workflow, all four archives and checksums, provenance, registry version, and an installed binary before reporting success.

Failed Publication And Recovery

Inspect the failed job and current GitHub/crates.io state before retrying. The two services cannot publish atomically. A workflow retry verifies an existing crate's checksum against the candidate before skipping its upload. Investigate a mismatch rather than bypassing that check. Do not replace an already published tag or delete a published release as routine recovery. Use a follow-up version for code fixes; yanking a broken crate requires explicit authorization.

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