Agent skill

Stax Dev

by cesarferreira in cesarferreira/stax

Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.

MITAuto-check passedDevelopment

Install Stax Dev

skills CLI
$ npx skills add cesarferreira/stax --skill stax-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cesarferreira/stax stax-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
stax-dev
GitHub stars
130
Token cost
~987 tokens
SKILL.md length
267 words
Files
2 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.

  • Works in 5 steps: Context Check → Plan → Implement → …
  • Any feature request
  • SKILL.md covers Phase 0: Context Check, Phase 1: Plan, Phase 2: Implement and Phase 3: Verify, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • Any feature request
  • Refactor in the stax codebase
  • : add a command
  • Implement X in stax

Example prompts

  • “add a command”
  • “implement X in stax”
  • “fix bug”
  • “/stax-dev”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Context Check
  2. Plan
  3. Implement
  4. Verify
  5. Fix Loop (if verifier reports failures)

What it can do on your machine

Read from SKILL.md and the folder at commit da27cb8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~987
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from cesarferreira/stax at commit da27cb8, republished under its MIT licence (© cesarferreira). 267 words, ~987 tokens.

Download SKILL.mdSave it as .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.
name
stax-dev
description
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.

stax-dev — Development Harness

Execution mode: Sub-agent pipeline — planner → implementer → verifier

Phase 0: Context Check

Before dispatching any agents, check for prior plan output:

bash
ls .claude/plans/stax-plan.md 2>/dev/null
  • If the file exists and the user's request is a follow-up ("fix the error", "retry", "it failed"), skip Phase 1 and use the existing plan.
  • Otherwise: start fresh. If .claude/plans/stax-plan.md exists from a different task, note this to the user.

Phase 1: Plan

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.

Phase 2: Implement

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.
  "
)

Phase 3: Verify

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.
  "
)

Phase 4: Fix Loop (if verifier reports failures)

If the verifier output contains failures:

  1. Show the user which checks failed.
  2. Dispatch the implementer again with the plan + verifier error report:
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.
  "
)
  1. Re-run Phase 3.
  2. Repeat up to 2 additional fix attempts (3 total). After the third failure, stop and present the remaining errors to the user for guidance.

Output to User

After completing the pipeline:

  1. Files changed: list from implementer's CHANGED/CREATED summary
  2. Verification: pass/fail with any remaining issues
  3. Next step suggestion if verification failed after max retries

Test Scenarios

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

Files

SKILL.md and 1 other file (references) in .claude/skills/stax-dev of cesarferreira/stax.

  • SKILL.md
  • references/patterns.md

Open the folder on GitHubat commit da27cb8

Compare with similar skills

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.

Stax Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stax Dev this skillcesarferreira/stax130—~987Automated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9.1k—~6.9kAutomated safety check: PassCustom licence
Git History Bug Auditben-manes/caffeine18k—~3.3kAutomated safety check: PassApache-2.0
BrDicklesworthstone/beads_rust1.1k—~2.7kAutomated safety check: PassMIT
Debug Tuitrasta298/keifu810—~1.3kAutomated safety check: PassMIT
Guarded Git Commit and Pushjerrywu001/cc-sessions-viewer395—~603Automated safety check: NotesMIT

Similar skills

  • 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.

    9.1k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Git History Bug Audit

    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.

    18k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Br

    Dicklesworthstone/beads_rust

    Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.

    1.1k GitHub stars~2.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Debug Tui

    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.

    810 GitHub stars~1.3k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Guarded Git Commit and Push

    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.

    395 GitHub stars~603 tokensUpdated 2 days ago
    DevelopmentAuto-check: notes
  • Radicle Ecosystem

    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.

    148 GitHub stars~574 tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Stax Dev

What does Stax Dev do?

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.

When should I use Stax Dev?

Stax Dev fits situations like: any feature request; refactor in the stax codebase; : add a command; implement X in stax.

How do I install Stax Dev in Claude Code?

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.

How do I install Stax Dev in Codex?

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.

Can I use Stax Dev in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Stax Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Stax Dev is instructions for the agent only.

Does Stax Dev access the network?

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.

Is Stax Dev safe to install?

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.

What licence does Stax Dev use?

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.

How many tokens does Stax Dev use?

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.

What are the alternatives to Stax Dev?

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.

Who maintains Stax Dev?

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.