docs: document updating + releasing (main already added the publish workflow)#24
Merged
Merged
Conversation
… current task A passing thought dropped mid-task reads as a new request, so the agent rushes the big task to get to it. /sidenote reframes it as a parked later-task: log it verbatim to .claude/sidenotes.md, one-line ack, resume with scope and pace unchanged. Bare /sidenote flushes the list. Wired into the installer (copy on install, remove on uninstall) and documented in the README alongside /scalable, including the plain-text SIDENOTE: prefix for agents without slash commands.
…times-i-think-about
fenceInto only stripped its own <!-- karpathy-skills --> block before re-appending, so running the installer against a file where the guidelines were hand-merged (verbatim '## 1. Think Before Coding' heading, no markers) appended a second full copy. Detect that heading outside our block and skip with a warning instead; wire up the previously-dead --force flag as the override. Mirrors the activate hook's dedup so both paths behave the same.
…times-i-think-about
…he parking file A verbatim thought parked mid-task is full of 'this / here / it' that dangles when another session or agent reads it cold. Each entry now carries a one-line anchor (task in progress, the file it points at, branch@sha) drawn only from context already in hand — no investigating, so the park contract holds. Entries use - [ ] / - [x]; a bare /sidenote flushes everything not checked off, so older un-checkboxed bullets still surface. Add a repo .gitignore for .claude/sidenotes.md so 'git add -A' can't sweep personal parked thoughts into shared history, and sync the README to match.
…times-i-think-about
The README advertised 'npx @clawnify/greybeard' but the package was never published (npm 404), so install/update had no working path. Add a release-driven publish workflow mirroring clawnify/clawnify's publish-cli / create-clawnify-app (release published + workflow_dispatch bootstrap, id-token: write, npm publish --access public --ignore-scripts via NPM_TOKEN), with a check-sync guard so drifted rule copies never ship. Document how to update each install path (npx @latest, the plugin marketplace-update/reinstall sequence, curl -o) and how maintainers cut a release.
…times-i-think-about
main already added .github/workflows/publish.yml (release-triggered npm publish with --provenance, build + check-sync + installer smoke test) while this branch was in flight. Remove the redundant publish-npm.yml this branch added — shipping both would double-publish on every release — and keep the README updating/releasing docs, repointed at publish.yml and without the workflow_dispatch bootstrap that publish.yml doesn't offer.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the Updating and Releasing docs to the README. The npm publish workflow itself (
.github/workflows/publish.yml) already landed on main separately while this branch was in flight — this branch no longer duplicates it.Changes
npx @clawnify/greybeard@latest(cache-safe), the Claude Code plugin update sequence (/plugin marketplace update greybeard→ uninstall → install →/reload-plugins; third-party marketplaces don't auto-update by default), and the curl-ooverwrite. Plus a maintainer Releasing note pointing atpublish.yml.publish-npm.ymlthis branch had added —main'spublish.ymlsupersedes it (it's the better version:--provenance,npm run build+ check-sync + installer smoke test). Shipping both would double-publish on every release.Context
Found while investigating "how should agents update to the latest Greybeard": the README advertised
npx @clawnify/greybeardbut the package wasn't on npm (404). The publish workflow (added on main) plus these docs close that gap. First publish: set theNPM_TOKENsecret, thengh release create v0.1.0.