Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.
$ npx skills add cesarferreira/stax --skill stax-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cesarferreira/stax stax-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cesarferreira/stax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/stax-dev .claude/skills/stax-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "stax-dev" agent skill from https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-dev into .claude/skills/stax-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stax-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cesarferreira/stax --skill stax-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cesarferreira/stax stax-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cesarferreira/stax.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/stax-dev .agents/skills/stax-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stax-dev" agent skill from https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-dev into .agents/skills/stax-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stax-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cesarferreira/stax --skill stax-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cesarferreira/stax stax-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cesarferreira/stax.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/stax-dev .cursor/skills/stax-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stax-dev" agent skill from https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-dev into .cursor/skills/stax-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stax-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cesarferreira/stax.git --path .claude/skills/stax-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cesarferreira/stax --skill stax-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cesarferreira/stax stax-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cesarferreira/stax.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/stax-dev .gemini/skills/stax-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stax-dev" agent skill from https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-dev into .gemini/skills/stax-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stax-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cesarferreira/stax stax-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cesarferreira/stax --skill stax-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cesarferreira/stax.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/stax-dev .github/skills/stax-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stax-dev" agent skill from https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-dev into .github/skills/stax-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stax-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cesarferreira/stax --skill stax-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cesarferreira/stax stax-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cesarferreira/stax.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/stax-dev .opencode/skills/stax-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stax-dev" agent skill from https://github.com/cesarferreira/stax/tree/main/.claude/skills/stax-dev into .opencode/skills/stax-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stax-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
stax-devDevelopment harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.
Stax Dev is an agent skill from cesarferreira/stax. Development harness for the stax Rust CLI project. Use for any feature request, bug fix, new command, code change, or refactor in the stax codebase. Triggers on: "add a command", "implement X in stax", "fix bug", "change how stax does Y", "make stax support Z", "update stax to", "I want stax to". Also triggers for follow-up work: "fix the error", "try again", "re-run", "update the implementation", "that didn't work". Do NOT trigger for pure questions about stax usage or git concepts.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/patterns.md`).
It sits in Development, covering Debugging and Git workflow. It works with Git and Rust. The repository describes itself as: The fastest stacked-branch workflow for Git. Interactive TUI, smart PRs, safe undo. Written in Rust. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit da27cb8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Stax Dev loads about 987 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 267 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from cesarferreira/stax at commit da27cb8, republished under its MIT licence (© cesarferreira). 267 words, ~987 tokens.
.claude/skills/stax-dev/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Execution mode: Sub-agent pipeline — planner → implementer → verifier
Before dispatching any agents, check for prior plan output:
ls .claude/plans/stax-plan.md 2>/dev/null.claude/plans/stax-plan.md exists from a different task, note this to the user.Dispatch the planner. Pass the user's full request verbatim plus the project root path.
Agent(
subagent_type: "stax-planner",
model: "opus",
prompt: "
Project root: /Users/cesarferreira/code/github/stax
Request: <user's full request verbatim>
Produce a complete implementation plan following your output format.
Read patterns.md at .claude/skills/stax-dev/references/patterns.md first.
"
)Save the plan text to .claude/plans/stax-plan.md (create the directory if needed).
Show the plan summary to the user before proceeding to Phase 2.
Dispatch the implementer with the full plan:
Agent(
subagent_type: "stax-implementer",
model: "sonnet",
prompt: "
Project root: /Users/cesarferreira/code/github/stax
Execute this implementation plan exactly:
---
<full plan content>
---
Read patterns.md at .claude/skills/stax-dev/references/patterns.md first.
Read each file before editing. Do not run build or tests.
Output the CHANGED/CREATED summary at the end.
"
)Dispatch the verifier:
Agent(
subagent_type: "stax-verifier",
model: "opus",
prompt: "
Project root: /Users/cesarferreira/code/github/stax
Verify the changes just implemented. Run cargo check, clippy, fmt --check,
then targeted tests with this filter: <Verification Steps from plan>.
Report all results per your reporting format.
"
)If the verifier output contains failures:
Agent(
subagent_type: "stax-implementer",
model: "sonnet",
prompt: "
Project root: /Users/cesarferreira/code/github/stax
The previous implementation had errors. Fix them.
Original plan:
---
<plan content>
---
Verifier errors to fix:
---
<verifier output>
---
Read each file before editing. Output the CHANGED summary.
"
)After completing the pipeline:
Normal flow: "Add a stax ping command that prints the current branch name"
→ Planner: identifies args.rs + mod.rs dispatch + new commands/ping.rs + commands/mod.rs
→ Implementer: creates the 4 files/edits
→ Verifier: cargo check + clippy pass, no targeted tests needed
Fix loop: Implementer misses a use import → verifier flags it → implementer adds it → verifier passes on second run.
© cesarferreira, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in .claude/skills/stax-dev of cesarferreira/stax.
Open the folder on GitHubat commit da27cb8
Stax Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stax Dev this skillcesarferreira/stax | 130 | — | ~987 | Automated safety check: Pass | MIT | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 9.1k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Git History Bug Auditben-manes/caffeine | 18k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| BrDicklesworthstone/beads_rust | 1.1k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Debug Tuitrasta298/keifu | 810 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Guarded Git Commit and Pushjerrywu001/cc-sessions-viewer | 395 | — | ~603 | Automated safety check: Notes | MIT |
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
Dicklesworthstone/beads_rust
Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.
trasta298/keifu
Drive and debug the real keifu TUI autonomously via its remote-control debug server (--debug-listen) — launch headlessly, inject keys/mouse, dump the rendered screen as text, and inspect app state.
jerrywu001/cc-sessions-viewer
Commits and pushes only on an explicit request, pulling first, running the project's CI checks locally, and stopping cold on any conflict or failure.
radicle-dev/radicle-explorer
Map of the sibling Radicle repositories that radicle-httpd depends on (heartwood, radicle-git, radicle-job, rips, radicle.dev), with the key crates and files to read in each.
Categories
Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax. Stax Dev is an agent skill from cesarferreira/stax. Development harness for the stax Rust CLI project.
Stax Dev fits situations like: any feature request; refactor in the stax codebase; : add a command; implement X in stax.
Run `npx skills add cesarferreira/stax --skill stax-dev -a claude-code`. Or copy the skill folder (.claude/skills/stax-dev in cesarferreira/stax) into .claude/skills/stax-dev in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cesarferreira/stax --skill stax-dev -a codex`. Or copy the skill folder (.claude/skills/stax-dev in cesarferreira/stax) into .agents/skills/stax-dev in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cesarferreira/stax --skill stax-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stax-dev, .gemini/skills/stax-dev, .github/skills/stax-dev and .opencode/skills/stax-dev in your project.
SKILL.md names no scripts, command-line tools or credentials: Stax Dev is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Stax Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 987 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 996 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Stax Dev: Worktrunk Release Workflow (max-sixty/worktrunk, 9.1k stars), Git History Bug Audit (ben-manes/caffeine, 18k stars), Br (Dicklesworthstone/beads_rust, 1.1k stars) and Debug Tui (trasta298/keifu, 810 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cesarferreira (a GitHub user) maintains it in cesarferreira/stax, which has 130 GitHub stars. The repository was last updated on October 8, 2026.
Source: cesarferreira/stax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.