Agent skill

Worktrunk Tend CI Guidance

by max-sixty in max-sixty/worktrunk

Adds Worktrunk-specific rules to the tend CI workflows: Codecov polling, Rust test commands, labels and review criteria for pull requests handled in CI.

Custom licenceAuto-check passedDevelopment

Install Worktrunk Tend CI Guidance

skills CLI
$ npx skills add max-sixty/worktrunk --skill running-tend -a claude-code

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

GitHub CLI
$ gh skill install max-sixty/worktrunk running-tend --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/max-sixty/worktrunk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/running-tend .claude/skills/running-tend && 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
running-tend
GitHub stars
9k
Token cost
~6.4k tokens
SKILL.md length
3,223 words
Files
3 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
Custom licence

At a glance

Adds Worktrunk-specific rules to the tend CI workflows: Codecov polling, Rust test commands, labels and review criteria for pull requests handled in CI.

  • Works in 5 steps: Search open and closed issues for the… → Draft the alias. → Test it in a scratch worktree against… → …
  • Running a tend workflow in CI on the Worktrunk repository
  • SKILL.md covers Filing issues in other repos, Codecov Monitoring, Test Commands and Rework a test that reaches for…, plus 14 more sections
  • Calls gh, cargo and git; reaches code.claude.com; needs WORKTRUNK_SECTION__KEY

What it does

This sits on top of the generic `tend-ci-runner` skills (run-tend, review, triage) and supplies the conventions for Worktrunk, a Rust CLI for managing git worktrees. After the required CI checks pass, the agent must also poll `codecov/patch`, which is mandatory even though it is not marked required. A standing exception lets it file issues directly in other repositories that show agent signals, without asking first.

When coverage fails in CI, `task` and `cargo-llvm-cov` are not installed, so the agent is told not to try compiling them and to query Codecov directly or download the `code-coverage-report` artifact with its `cobertura.xml` instead. Test commands are listed: `cargo run -- hook pre-merge --yes` for the full suite and lints, `cargo test --lib --bins` for unit tests and `cargo test --test integration` for integration tests, with CI on Linux, Windows and macOS. Reference files cover the nightly cleaner and PR review.

When your agent uses it

  • Running a tend workflow in CI on the Worktrunk repository
  • Waiting for the Codecov patch check after required checks pass
  • Choosing the right cargo command for unit or integration tests
  • Reviewing a Worktrunk pull request against the project's criteria

Example prompts

  • “The required checks are green on this PR. Poll codecov/patch and tell me whether coverage passed.”
  • “Codecov failed on my PR and task is not installed in CI. How do I find the uncovered lines?”
  • “Run only the integration tests for worktrunk and report the result.”

Requirements

  • The tend-ci-runner skills
  • The GitHub CLI (`gh`) in the CI environment
  • Cargo for the Rust test commands

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Search open and closed issues for the same request and link the prior
  2. Draft the alias.
  3. Test it in a scratch worktree against the happy path and edge cases (branch
  4. Post the tested alias with usage examples.
  5. Link to the aliases docs and

What it can do on your machine

Read from SKILL.md and the folder at commit 4f4611e. 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

    Shell commands in SKILL.md call:

    • gh
    • cargo
    • git
    • nix
    • jq
    • npm
    • uvx
    • codex
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • code.claude.com

    Also links to:

    • worktrunk.dev
    • docs.anthropic.com
    • developers.openai.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • WORKTRUNK_SECTION__KEY

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

Context cost

Worktrunk Tend CI Guidance loads about 6.4k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 3,223 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,223 words (~6,423 tokens).

“Project-specific guidance for tend workflows running on worktrunk (a Rust CLI for managing git worktrees). The generic skills (/tend-ci-runner:run-tend, /tend-ci-runner:review, /tend-ci-runner:triage, etc.) provide the workflow framework; this skill adds worktrunk conventions.”

— opening of SKILL.md by max-sixty, Custom licence
name
running-tend
metadata.internal
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in .claude/skills/running-tend of max-sixty/worktrunk.

  • SKILL.md
  • references/nightly-cleaner.md
  • references/review-pr.md

Open the folder on GitHubat commit 4f4611e

Compare with similar skills

Worktrunk Tend CI Guidance 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.

Worktrunk Tend CI Guidance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Worktrunk Tend CI Guidance this skillmax-sixty/worktrunk9k—~6.4kAutomated safety check: PassCustom licence
Code ReviewAzure/sap-automation145—~7kAutomated safety check: PassMIT
Project Initathola/claude-night-market342—~1.2kAutomated safety check: PassMIT
Reviewwerf/werf4.7k—~2kAutomated safety check: PassApache-2.0
Code Reviewpolyipseity/obsidian-terminal948—~1.6kAutomated safety check: PassAGPL-3.0
Code Reviewoaslananka/kicad-mcp-pro120—~3.9kAutomated safety check: PassMIT

Similar skills

  • Code Review

    Azure/sap-automation

    Official

    Review pull requests in the SAP Deployment Automation Framework.

    145 GitHub stars~7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Project Init

    athola/claude-night-market

    Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config.

    342 GitHub stars~1.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Review

    werf/werf

    Code review of a pull request, branch, or diff. An agent skill from werf/werf.

    4.7k GitHub stars~2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Code Review

    polyipseity/obsidian-terminal

    A skill your agent uses when reviewing PRs, code changes, or conducting code audits in obsidian-terminal.

    948 GitHub stars~1.6k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Code Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.

    120 GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Sendou Code Review

    sendou-ink/sendou.ink

    Multi-agent code review that checks the current diff from multiple angles (spec compliance, bugs from two lenses, conventions/modernization, abstraction reuse, security, DB query performance, test…

    297 GitHub stars~5.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from max-sixty/worktrunk

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

    9k GitHub stars~6.9k tokensUpdated today
    Auto-check passed
  • Worktrunk CLI Output Rules

    max-sixty/worktrunk

    CLI output standards for worktrunk: message functions, ANSI color nesting and the shell integration that changes directory after the wt command exits.

    9k GitHub stars~12k tokensUpdated today
    Auto-check passed

Works with

Questions about Worktrunk Tend CI Guidance

What does Worktrunk Tend CI Guidance do?

Adds Worktrunk-specific rules to the tend CI workflows: Codecov polling, Rust test commands, labels and review criteria for pull requests handled in CI. This sits on top of the generic `tend-ci-runner` skills (run-tend, review, triage) and supplies the conventions for Worktrunk, a Rust CLI for managing git worktrees. After the required CI checks pass, the agent must also poll `codecov/patch`, which is mandatory even though it is not marked required.

When should I use Worktrunk Tend CI Guidance?

Worktrunk Tend CI Guidance fits situations like: running a tend workflow in CI on the Worktrunk repository; waiting for the Codecov patch check after required checks pass; choosing the right cargo command for unit or integration tests; reviewing a Worktrunk pull request against the project's criteria.

How do I install Worktrunk Tend CI Guidance in Claude Code?

Run `npx skills add max-sixty/worktrunk --skill running-tend -a claude-code`. Or copy the skill folder (.claude/skills/running-tend in max-sixty/worktrunk) into .claude/skills/running-tend in your project. Claude Code loads it when a task matches its description.

How do I install Worktrunk Tend CI Guidance in Codex?

Run `npx skills add max-sixty/worktrunk --skill running-tend -a codex`. Or copy the skill folder (.claude/skills/running-tend in max-sixty/worktrunk) into .agents/skills/running-tend in your project. Codex loads it when a task matches its description.

Can I use Worktrunk Tend CI Guidance 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 max-sixty/worktrunk --skill running-tend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/running-tend, .gemini/skills/running-tend, .github/skills/running-tend and .opencode/skills/running-tend in your project.

What does Worktrunk Tend CI Guidance need to run?

Going by SKILL.md and its folder, Worktrunk Tend CI Guidance needs the command-line tools its instructions call (gh, cargo, git, nix, jq and npm) and credentials named WORKTRUNK_SECTION__KEY. Our summary lists: The tend-ci-runner skills; The GitHub CLI (`gh`) in the CI environment; Cargo for the Rust test commands.

Does Worktrunk Tend CI Guidance access the network?

SKILL.md names 4 domains. In commands or code: code.claude.com; the agent is likely to contact it when it follows the instructions. As links in the text: worktrunk.dev, docs.anthropic.com and developers.openai.com. This is read from the text; nothing was executed.

Is Worktrunk Tend CI Guidance 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 Worktrunk Tend CI Guidance use?

Worktrunk Tend CI Guidance has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Worktrunk Tend CI Guidance use?

About 6.4k tokens (SKILL.md is roughly 26k 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 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Worktrunk Tend CI Guidance?

Skills that share tags, products or a category with Worktrunk Tend CI Guidance: Code Review (Azure/sap-automation, 145 stars), Project Init (athola/claude-night-market, 342 stars), Review (werf/werf, 4.7k stars) and Code Review (polyipseity/obsidian-terminal, 948 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Worktrunk Tend CI Guidance?

max-sixty (a GitHub user) maintains it in max-sixty/worktrunk, which has 8,977 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.

Source: max-sixty/worktrunk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.