running-tend

Applies worktrunk-specific conventions to tend CI workflows including codecov polling, triage, and weekly maintenance.

6.8k|240|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/max-sixty/worktrunk --skill running-tend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: running-tend
Source: https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/running-tend
Command: npx skills add https://github.com/max-sixty/worktrunk --skill running-tend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Running automated CI agents on the worktrunk repository requires project-specific knowledge that generic tend workflow skills lack: which checks are mandatory despite being non-required, how to classify CI failures, which test commands to run, and how to handle worktrunk's weekly maintenance tasks like MSRV bumps and CI pin updates.

Core Features & Use Cases

  • Codecov Monitoring: Polls the mandatory codecov/patch check after required CI passes, with instructions for investigating failures via the Codecov API or downloading cobertura.xml coverage artifacts.
  • CI Failure Classification: Distinguishes transient infrastructure failures (rerun, no PR) from flaky tests and real regressions before opening fix/ci-* PRs.
  • Issue Triage Guidance: Leads with wt -vv <command> diagnostic bundles, handles duplicates, suggests wt aliases for niche feature requests, and refuses unverifiable fixes.
  • Weekly Maintenance: Covers MSRV/toolchain bumps, CI pin updates, statusline cache checks, LLM model name drift, and agent app integration surface scans.
  • Use Case: A tend CI agent reviewing a worktrunk PR uses this skill to know it must wait for codecov/patch, apply GitHub suggestions literally, and hold data-loss-surface changes for human review.

Quick Start

Use the running-tend skill to review this worktrunk pull request following the project's CI and review conventions.

Frequently Asked Questions about running-tend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor codecov/patch checks in CI?

Poll `gh pr checks <number>` in a loop grepping for `codecov/patch` until it reports pass or fail, sleeping 60 seconds between attempts. The check is mandatory for worktrunk despite being marked non-required, so wait for it after required checks pass.

How do I classify a CI failure before opening a fix PR?

Classify failures as transient infrastructure (link-check timeouts, runner disk issues), flaky tests, or real regressions. Only open a fix PR for real regressions; transient failures should be left for the maintainer to rerun, and non-required status does not imply transient.

What should I ask for when triaging a worktrunk bug report?

Ask the reporter to run `wt -vv <command>`, which writes a diagnostic bundle with versions, config, worktree state, and a trace log. Point them at the printed gist command rather than a hardcoded path, since `.git` is a file inside linked worktrees.

When should a PR touching deletion commands be held for review?

Hold any PR whose diff adds or widens force-delete operations like `wt remove -D`, `git reset --hard`, or `rm -rf` when it can reach user data that cannot be regenerated. Request review from the maintainer and do not approve or merge.

How are MSRV and toolchain versions bumped in weekly maintenance?

Set both MSRV and the development toolchain to latest stable minus one, updating `rust-version` in Cargo.toml files, `channel` in rust-toolchain.toml, and nightly pins in nightly.yaml. Then refresh flake.lock with `nix flake update rust-overlay` and run the full test suite.