chore: add create-pr, eli5, quickwins, and release workflow skills#93
Merged
Conversation
Three project-level skills capturing recurring workflows in this repo: - create-pr: branch off main, run the gates, commit with the Co-Authored-By footer, push, and open a PR with the 🤖 footer and a Closes #N link; reports mergeable without merging (repo convention), and ends with a brief ELI5 to read while CI runs. - eli5: plain-English, jargon-free explanation of a PR/diff/code/concept. - quickwins: scan a milestone/backlog, triage genuine quick wins from disguised epics, recommend a next step, and hand off to create-pr. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Captures this repo's two-phase release flow: a prepare PR off a release/X.Y.Z branch (Cargo version bump, Cargo.lock refresh, scripts/bump-docs-version.sh, CHANGELOG cut + compare links), then a gated tag-and-push of vX.Y.Z that fires release.yml. The tag phase is behind explicit confirmation since it publishes to npm + GitHub Releases and dispatches the surface-site docs sync. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Connorrmcd6
changed the title
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.
Adds four project-level skills under
.claude/skills/, each capturing a workflow we've been running by hand in this repo:create-pr— branch offmain→ run the gates → commit with theCo-Authored-Byfooter → push → open a PR with the 🤖 footer andCloses #N. Encodes the standing rule (report mergeable, don't merge; verify CI green if asked), and ends each run with a brief ELI5 to read while CI runs.eli5— plain-English, jargon-free explanation of a PR/diff/code/concept; defaults to "what we just did".quickwins— scan a milestone/backlog, triage genuine quick wins from disguised epics, recommend a next step, and hand off tocreate-pr.release— the two-phase release flow: a prepare PR offrelease/X.Y.Z(Cargo version bump,Cargo.lockrefresh,scripts/bump-docs-version.sh, CHANGELOG cut + compare links), then a confirmation-gated tag-and-push ofvX.Y.Zthat firesrelease.yml. Tagging is gated because it publishes to npm + GitHub Releases and dispatches the surface-site docs sync; it also flags the known npm-visibility flake (npm channel: publish succeeds and CI is green, but the registry has zero versions — npx @gradient-tools/surface fails ENOVERSIONS #80).Verification
Docs/skills-only change — no Rust touched, so the
fmt/clippy/testgates have nothing to act on. EachSKILL.mdhas valid frontmatter (name+description);/reload-skillspicked the first three up (the fourth lands on next reload).🤖 Generated with Claude Code