agentleFS
NikiforovAllNikiforovAll/redline/.claude/skills/release/SKILL.md

release

Skill3 starsChanged 59 days agoMITView on GitHub

Cut a redline release from this checkout: bump, build, test, commit, then push the tag that makes the Release workflow publish npm, marketplace, and GitHub release, after one confirmation.

  • Installs packages

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 1

    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:

    Stop at the first failure and report the line that failed.

    line 16

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

release

Ship the extension and the server under one version. The laptop bumps, checks, commits, and pushes the tag v<version>; the Release workflow (.github/workflows/release.yml) packages the vsix and publishes @nikiforovall/redline-mcp to npm, the extension to the VS Code marketplace, and the .vsix to a GitHub release. Nothing is packaged or published from the laptop. The plugin has its own version and only pins the server; docs/PUBLISHING.md, section "Two versions", has the reasons.

$ARGUMENTS is the bump level (patch when empty, minor, major) or an explicit X.Y.Z, plus flags: --plugin also moves the plugin to its next patch so installed plugins pick up the new pin; --dry-run ends the run after the checks with the bump left in the working tree.

Preflight

Stop at the first failure and report the line that failed.

  • The branch is main and git -C <root> status --porcelain is empty, or lists only the Bump files already at <version> from an earlier run that stopped before publishing; then skip Bump.
  • gh auth status reports a login.
  • npm run check:versions prints one version: extension, server, and pin.json agree before anything moves.
  • <version> is that printed version plus the bump level, or the explicit one, which must be higher.
  • npm view @nikiforovall/redline-mcp@<version> version fails and git -C <root> ls-remote --tags origin v<version> prints nothing: neither the registry nor the remote has the version yet.

Bump

Edit the "version" line in each file with the Edit tool. npm version rewrites the manifests in expanded JSON and produces a 40-line diff, so it stays out of this step.

  1. packages/extension/package.json and packages/mcp/package.json to <version>.
  2. packages/claude-plugin/scripts/pin.json so @nikiforovall/redline-mcp is <version>.
  3. npm install --package-lock-only so the lockfile carries the new versions.
  4. With --plugin, version in packages/claude-plugin/.claude-plugin/plugin.json to its next patch.

Done when git -C <root> diff --stat lists the two manifests, the lockfile, pin.json, and with --plugin plugin.json, each with one changed line, and npm run check:versions prints <version>.

Check

<log> is a file in the session scratchpad directory; the test output is long and only its summary lines matter.

npm run build
npm test > "<log>" 2>&1; echo "npm test exit $?"; rg '^ℹ (pass|fail) ' "<log>"

Done when the test exit is 0 with three fail 0 lines. With --dry-run, report and stop here.

Confirm

Show the bump diff stat and the test summary, then ask one question with AskUserQuestion: push v<version> now, or stop. Skip the question when the user's request already says to publish. Nothing so far has left the machine. Everything after is irreversible: the tag triggers the workflow, and npm never accepts a version twice.

Publish

git -C <root> add -A && git -C <root> commit -m "chore: release v<version>"
git -C <root> push origin main
git -C <root> tag -a v<version> -m v<version> && git -C <root> push origin v<version>
gh run list --workflow Release --limit 1 --json databaseId,headBranch,status
gh run watch <id> --exit-status --interval 15

Run them in order and stop at the first non-zero exit. The run list can lag the push by a few seconds; its headBranch must be the tag before watching. Every publish step in the workflow skips a version that already exists, so a failed run is fixed by fixing the cause and gh run rerun <id>, never by a new tag.

Done when the run is green and these three agree with <version>; the registry and the marketplace index a minute or two after the run, so retry them with a pause between attempts:

npm view @nikiforovall/redline-mcp version
npx vsce show nikiforovall.redline-extension --json | rg '"version": "<version>"'
gh release view v<version> --json assets -q '.assets[].name'

Report

One line per artifact: npm version, marketplace version, release URL, plugin version and whether it moved. Then how users get it: the extension from the marketplace (VS Code updates it on its own); the server on the next plugin bump unless --plugin shipped it now.

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.