agentleFS
nwiizonwiizo/claudelytics/.claude/skills/deploy-check/SKILL.md

deploy-check

Skill88 starsChanged 8 months agoMITView on GitHub

Pre-release verification workflow - version, security audit, performance, cross-platform builds, documentation.

9 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, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Run pre-release verification.

    line 10
  2. Distinctive:

    Verify version is bumped appropriately

    line 18
  3. Distinctive:

    Ensure CHANGELOG.md is updated with release notes

    line 19
  4. Distinctive:

    All new features are documented

    line 49

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

Deploy/Release Check

Run pre-release verification. Focus area: $ARGUMENTS

Step 1: Version & Changelog

grep version Cargo.toml
  • Verify version is bumped appropriately
  • Ensure CHANGELOG.md is updated with release notes

Step 2: Security Audit

cargo audit
cargo outdated --exit-code 1

Step 3: Performance Verification (parallel)

cargo build --release
ls -lh target/release/claudelytics
cargo bench

Step 4: Cross-Platform Build Test (parallel)

cargo build --release --target x86_64-unknown-linux-gnu
cargo build --release --target x86_64-unknown-linux-musl
cargo build --release --target x86_64-pc-windows-msvc
cargo build --release --target x86_64-apple-darwin
cargo build --release --target aarch64-apple-darwin

Step 5: Documentation

  • README.md is up to date
  • All new features are documented
  • cargo doc --no-deps succeeds

Step 6: Release Assets

shasum -a 256 target/release/claudelytics-*

Final Checklist

  • All tests pass in release mode (cargo test --release)
  • No security vulnerabilities
  • Documentation complete
  • Version bumped
  • CHANGELOG.md updated
  • Release binaries build successfully

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.