Release

Skill guillempuche/ai-standards/.claude/skills/release

Open-source AI coding skills for Claude Code, Cursor, Copilot, and AI agents

Install

npx -y skills add guillempuche/ai-standards --skill release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Detect changes in skills/agents, ask about version bumps, update frontmatter versions, and deploy individual repos to GitHub.

SKILL.md

2.9 KB, as published. Nobody here has run it

Release Workflow

Detect changes, bump versions, and deploy individual plugin repos.

Step 1: Identify changed repos

Map user arguments to repo names. The user may pass source paths (agents/readability-improver.md, skills/tamagui) or repo names (ai-agent-readability-improver). Convert source paths to repo names:

agents/<name>.md → ai-agent-<name>
skills/<name> → ai-skill-<name>

Generate the targeted dist-repos:

./scripts/generate-individual-repos.sh <repo-names...>

Then compare each against cache:

for repo_name in <repo-names...>; do
  cache_dir=".repo-cache/$repo_name"
  repo_dir="dist-repos/$repo_name"
  if [ -d "$cache_dir" ]; then
    changes=$(diff -rq --exclude='.git' "$cache_dir" "$repo_dir" 2>/dev/null)
    if [ -n "$changes" ]; then
      echo "CHANGED: $repo_name"
      echo "$changes"
    fi
  else
    echo "NEW: $repo_name"
  fi
done

If no repos have changes, tell the user "Nothing to release" and stop.

Step 2: Show change summary

For each changed repo, show a brief summary of what changed (files added/modified/removed).

Step 3: Ask about version bumps

For each changed repo, use AskUserQuestion to ask the user what kind of version bump to apply:

patch (1.0.0 -> 1.0.1): Bug fixes, minor content updates
minor (1.0.0 -> 1.1.0): New content, features, or significant updates
major (1.0.0 -> 2.0.0): Breaking changes or complete rewrites

Step 4: Update source frontmatter

For each repo that needs a bump, update the version field in the source file:

Skills: skills/<name>/SKILL.md
Agents: agents/<name>.md

Use the Edit tool to change the version: line in the YAML frontmatter.

Compute the new version by parsing the current version: X.Y.Z and incrementing the appropriate part:

patch: increment Z
minor: increment Y, reset Z to 0
major: increment X, reset Y and Z to 0

Step 5: Bump main plugin.json

Ask the user if they want to bump the main .claude-plugin/plugin.json version too (patch/minor/major/skip). Update the "version" field if they choose to bump.

Step 6: Regenerate dist-repos

Run the generate script again with only the changed repos so dist-repos picks up the new versions:

./scripts/generate-individual-repos.sh <changed-repo-names...>

Step 7: Commit version bumps

Stage and commit all version changes in the main repo:

git add skills/ agents/ .claude-plugin/plugin.json
git commit -m "Bump versions for release

Co-Authored-By: Claude <[email protected]>"

Step 8: Deploy

Run the deploy script with only the changed repos:

./scripts/deploy-individual-repos.sh <changed-repo-names...>

Step 9: Push main repo

git push origin main

Show the user a summary of what was released with the new version numbers.

Gives 0 of the 12 instructions most ship operate skills give

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-06

document a rollback plan before deploymentin 40 of 779, across 21 files
create an annotated git tagin 21 of 779, across 20 files
Run the test suitein 20 of 779
update the changelogin 20 of 779, across 18 files
verify deployment health after launchin 19 of 779, across 10 files
clean up feature flags after full rolloutin 18 of 779, across 10 files
verify the working tree is cleanin 18 of 779
test both feature flag statesin 17 of 779, across 9 files
Make database migrations backward-compatiblein 16 of 779, across 8 files
set up error monitoring before launchin 15 of 779, across 7 files
monitor metrics at each rollout stagein 14 of 779, across 5 files
create a github releasein 14 of 779

Said here and by no other author read

convert user arguments to repo names
generate targeted dist-repos
compare generated repos against cache
show change summary for changed repos
update version field in source frontmatter
ask user about main plugin version bump

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.