agentsclimarketplace

Release

Skill tomplex/lgtm/.claude/skills/release

Use when the maintainer asks to "release lgtm", "cut a release for lgtm", or "ship a new lgtm version". Drives the full release process: pre-flight gates, version bump, CHANGELOG entry, commit, tag, push, and GitHub Release. Maintainer-only — do not invoke for unrelated requests.From its SKILL.md

Install
npx -y skills add tomplex/lgtm --skill release

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 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.

SKILL.md

7.2 KB, as published. Nobody here has run it

Releasing lgtm

You are about to cut a release of the lgtm Claude Code plugin. Follow these steps in order. If any gate fails, stop and report — do not skip ahead.

How releases reach coworkers

The plugin is consumed via the faradayio/fdy-skills marketplace as a github source. Claude Code pulls HEAD of main and uses .claude-plugin/plugin.json's version field as the cache key. The version bump in plugin.json is the only thing that delivers the change to coworkers. Tags and GitHub Releases are humans-only — they exist for visibility and subscribable notifications.

Note: v0.1.1 may have no GitHub Release — it was tagged retroactively and the Release was opt-in during bootstrap. gh release list missing v0.1.1 is expected; don't try to backfill it from a future release run.

Process

1. Pre-flight gate

Run each command. Stop on the first failure.

git rev-parse --abbrev-ref HEAD     # must print 'main'
git status --porcelain              # must be empty
git fetch origin
git status                          # must say 'up to date with origin/main'
npm run build                       # must produce no diff
git status --porcelain              # still must be empty after the build

If npm run build dirties dist/ or frontend/dist/: stop. Tell the maintainer to commit the rebuilt output as a separate build: commit, then re-invoke this skill. Bundling 50k+ LOC of rebuilt dist with a 2-line version bump makes the release commit unreviewable.

2. Quality gates

npm test
npm run lint

Either failure → stop, surface the output, do not proceed.

3. Marketplace install smoke test

Verifies the github-source install path coworkers actually use: clean container, SessionStart hook fires, server boots, routes serve. Catches bugs that pass unit tests but break a fresh /plugin update install — the class of bug behind issues #1 and #2.

./scripts/test-marketplace-install.sh

Requires Docker. Expected runtime ~60s. Look for ALL CHECKS PASSED at the end; anything else is a fail — surface output and stop, no version bump.

If Docker isn't running: do not silently skip. Tell the maintainer Docker is required for this gate and abort. Skipping has cost coworkers time twice already (#1 and #2 were install-path bugs unit tests didn't catch).

4. Pick the bump level

PREV_TAG=$(git describe --tags --abbrev=0)
git log --oneline "${PREV_TAG}..HEAD"
git log --format="%s" "${PREV_TAG}..HEAD" | grep -oE '^[a-z]+' | sort | uniq -c

Show the maintainer:

  • The full commit list since the last tag
  • The prefix histogram (e.g., feat: 2, fix: 1, chore: 3) as a suggestion only

Do not infer silently. Ask: "Bump as patch, minor, or major?"

Why: chore: / build: / style: commits regularly carry behavior changes (e.g., a rebuilt dist/ lands as build: even when the underlying source change was a feat:). Auto-inference would mis-tag.

Semver policy:

  • Patch — bug fixes, doc updates, internal refactors, dep bumps that don't change behavior
  • Minor — new MCP tools, new UI features, new analysis modes, additive REST endpoints, new skills, new SSE events
  • Major — removed or renamed MCP tools, breaking on-disk DB schema (~/.lgtm/data.db), changed REST contract shape

5. Bump versions

Edit both files to the new X.Y.Z:

  • package.json → "version": "X.Y.Z"
  • .claude-plugin/plugin.json → "version": "X.Y.Z"

6. Compose the CHANGELOG entry

Read CHANGELOG.md. Prepend a new entry under the top heading section using Keep a Changelog format:

## [X.Y.Z] - YYYY-MM-DD

### Added
- (new features)

### Changed
- (behavior changes)

### Fixed
- (bug fixes, with issue links if applicable)

### Removed
- (removed features — major bump only)

Source the entries from git log "${PREV_TAG}..HEAD". Group by intent (features → Added, fixes → Fixed, etc.). Reference issue numbers (#1, #2) where commits cite them. Drop empty subsections.

7. Commit

git add package.json .claude-plugin/plugin.json CHANGELOG.md
git commit -m "release: vX.Y.Z"

Single-line commit message per repo convention.

8. Tag

Read the new CHANGELOG entry (everything between ## [X.Y.Z] and the next ## [ heading or EOF). Use that as the tag message body:

git tag -a --cleanup=verbatim "vX.Y.Z" -m "<changelog entry body>"

--cleanup=verbatim is required: without it, git tag strips lines starting with #, which would eat ### Fixed / ### Changed markdown headers from the message.

9. Push

git push origin main --follow-tags

If the push is rejected (divergence from origin):

git tag -d "vX.Y.Z"

Delete the local tag immediately so the next release's git log v_prev..HEAD math doesn't drift. Then abort and tell the maintainer to resolve the divergence first.

10. GitHub Release

gh release create "vX.Y.Z" \
  --title "vX.Y.Z" \
  --notes "<changelog entry body>"

If this fails: the release commit + tag are already on origin/main, so /plugin update consumers will get the change. Surface the error and tell the maintainer to retry just the gh step manually.

11. Announce on Slack

Compose this message:

lgtm vX.Y.Z is out — <one-line summary of the most user-visible change>.
Run /plugin update to pull. Notes: <github release URL>

The "user-visible change" should match what coworkers actually notice when they update — favor the headline feat: or user-facing fix: from the CHANGELOG, not internal refactors.

Default channel: #claude-code-users (private, channel ID C09LPD70FJ6). Confirm with the maintainer before posting — Slack posts are visible to others and need explicit go-ahead per global rules. If the maintainer wants a different channel, find the ID with slack_search_channels (include private_channel in channel_types).

Posting: use the Slack MCP slack_send_message tool with the channel ID and the composed message. If the Slack MCP is unavailable in this session, emit the template for the maintainer to paste manually instead.

fdy-skills/marketplace.json has no version field for lgtm — Claude Code falls back to plugin.json's version on the upstream repo (the only source of truth). Nothing to sync there.

Failure summary

FailureWhat to do
Tests / lint / build failStop, surface output, no version bump
npm run build dirties distStop, ask maintainer to commit build: separately
Working tree dirty pre-flightStop, ask maintainer to commit or stash
Marketplace install smoke test failsStop, surface output, no version bump
Docker not available for smoke testStop, do not skip silently — abort and ask maintainer to start Docker
Push rejectedgit tag -d vX.Y.Z, abort
gh release create fails after pushRelease is live; retry gh step manually

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.