All authors

Claude Skills by wine-fall
github.com/wine-fall7 skills0 installs9 views
- Create PrUse when opening, pushing, or updating a GitHub pull request for the murmur repo (after a local commit is ready) — including when a PR's CI "check / Validate PR title + description" fails, or when a `gh pr edit --body` silently does nothing.Votes: 0GitHub stars: 5
- Murmur Build SpecUse whenever the user asks to implement, build, work on, continue, or test any murmur spec — the request MUST name a target spec (e.g. `01`, `02`, `01-core-loop`, `L0`, `L1`). Also triggers on `/murmur-build-spec <id>`. This is the spec-driven build discipline for the murmur project: read the named spec first, build against it, and keep the spec and the code aligned (update the spec when a better direction emerges).Votes: 0GitHub stars: 5
- Murmur HandoffUse when the user wants to hand off work to a fresh session — asks to "hand off", "write a handoff", "prep a prompt for another session", or types /murmur-handoff. Produces ONE self-contained prompt the user can paste into a new murmur session and run directly. With args, it captures the stated handoff requirements; with no args, it infers the next step from this session.Votes: 0GitHub stars: 5
- Murmur IssueUse when a murmur bug, feature, or debt needs recording, discharging, or auditing — the user reports a bug or asks for a feature ('file an issue', 'record this bug', in any language), a build leaves behind an owed by-ear pass, a measured defect, or a watch item, an issue is being closed with a verdict, or someone asks "what is still open?". Also triggers on /murmur-issue. Owns the loop between GitHub issues and the `## Open` section of specs/STATUS.md; not for work that starts and finishes in...Votes: 0GitHub stars: 5
- Murmur ReleaseUse when cutting a murmur release — "release 0.1.3", "ship a version", "cut a release", "publish to npm", "tag a release" (in any language), or /murmur-release. Owns the whole ritual: the version decision, the release PR, the tag, the GitHub Release with notes, and the npm publish. Not for ordinary PRs (that is murmur-ship).Votes: 0GitHub stars: 5
- Murmur ShipUse when implementing, continuing, or shipping any murmur build task or spec step end-to-end — taking a named target (a spec/step, or the direction just agreed in this session) all the way to a delivered PR: build, test, review, commit, open the PR, and follow CI to a terminal state. Also triggers on /murmur-ship.Votes: 0GitHub stars: 5
- Murmur SmokeUse when you need to see murmur's REAL behavior instead of the fakes the unit suite uses — the real Claude brain (run_task / run_guide via claude-agent-sdk), real yt-dlp, audio playback, or the interactive guide — or when a change is unit-test-green but might be broken at the claude-agent-sdk / real-integration boundary, or you're troubleshooting a real-run failure or a stochastic/sensory behavior. The murmur companion to writing unit tests (murmur-build-spec).Votes: 0GitHub stars: 5