New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Work Issues

by go-to-k in go-to-k/cdkd

Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting…

Apache-2.0Auto-check passedDevelopment

Install Work Issues

skills CLI
$ npx skills add go-to-k/cdkd --skill work-issues -a claude-code

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

GitHub CLI
$ gh skill install go-to-k/cdkd work-issues --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/go-to-k/cdkd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/work-issues .claude/skills/work-issues && 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
work-issues
GitHub stars
143
Token cost
~1.7k tokens
SKILL.md length
915 words
Files
11 (incl. references)
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting…

  • Asked to handle/address filed issues
  • SKILL.md covers Launch mode: main checkout, or…, How this skill is packaged…, Stages and Hard invariants (hold even…
  • Calls git and gh
  • Not to hunt for new bugs (that is /hunt-bugs)

What it does

Work Issues is an agent skill from go-to-k/cdkd. Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting (collision-safe with other agents), verify against real AWS, then carry each through merge → pull → rebuild the linked binary → worktree cleanup. Use when asked to "handle/address filed issues", not to hunt for new bugs (that is /hunt-bugs).

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/claim.md`, `references/filing.md` and `references/gates-and-pr.md`).

It sits in Development, covering Git worktrees. It works with Amazon Web Services, GitHub, AWS CloudFormation and Git. The repository describes itself as: Drop-in CDK CLI for existing CDK apps — up to 15x faster deploys via direct AWS SDK calls instead of CloudFormation. The licence is Apache-2.0.

When your agent uses it

  • Asked to handle/address filed issues
  • Not to hunt for new bugs (that is /hunt-bugs)

Example prompts

  • “handle/address filed issues”
  • “/work-issues”

What it can do on your machine

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

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    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

Work Issues loads about 1.7k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 915 words of instructions outside code blocks.

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

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 go-to-k/cdkd at commit c1b6c57, republished under its Apache-2.0 licence (© go-to-k). 915 words, ~1,707 tokens.

Download SKILL.mdSave it as .claude/skills/work-issues/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
work-issues
description
Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting (collision-safe with other agents), verify against real AWS, then carry each through merge → pull → rebuild the linked binary → worktree cleanup. Use when asked to "handle/address filed issues", not to hunt for new bugs (that is /hunt-bugs).
argument-hint
[optional focus, e.g. 'destroy issues' | '#651 #650' | 'provider FPs']

Work Filed Issues

Drive as many OPEN issues as the run can carry to merged, released, installed fixes. The differentiator over "fix issue #N" is safe, collision-free PARALLELISM.

The golden rule: decide the set FIRST, claim it on the issues, THEN edit. The issue comment is the lock — it is what stops two agents fixing the same thing and colliding on the same file.

Launch mode: main checkout, or already inside a worktree

The flow creates one worktree per lane — right from the MAIN checkout, wrong when the launch location is ALREADY a linked worktree (an Orca/ADE workspace, a stray cd): git worktree add then NESTS one, and deleting the outer workspace takes the inner directory and its uncommitted work with it.

The PARENT computes which case applies BEFORE stage 0: read references/launch-mode.md and run the probe it holds (the ONLY copy).

  • Before stage 0, because §2's collision scan consumes the answer: IN-PLACE its relative .claude/worktrees/<w> paths resolve to nothing and the scan reports an empty board, reading as "no competing agents".
  • In the PARENT, because stages 0–3 go to a read-only subagent whose return payload carries no git state, so an answer computed there never reaches the party running git worktree add.

State all five printed values — MODE, which is MAIN-CHECKOUT or IN-PLACE, plus LANE_TREE, MAIN_CHECKOUT, LAUNCH_BRANCH (the branch §9 puts back; empty if launched detached) and ORIGIN (not go-to-k/cdkd means a fork run) — in the opening report, written after the probe and before any lane starts, and pass them into the triage dispatch and every lane dispatch. That report is their only recorded copy.

IN-PLACE changes the collision scan's paths, the claim, the branch recipe, the cleanup step, how main is reached, and where the retro branch is created; references/launch-mode.md maps each consequence to the stage that fires it.

How this skill is packaged (read this before stage 0)

This file is a thin orchestrator; the procedure lives in per-stage files under references/. Reading the stage file at stage entry is MANDATORY — the summaries below are not executable on their own. A bare §N points into the file that holds that section.

Delegate for context; keep the locks and the serialization in the parent.

  • Triage (stages 0–3): a read-only subagent. Prompt: read references/triage.md in full, execute it, and return ONLY the candidate table — per issue: number, title, target files, rank plus the deciding rule, collision evidence, premise-check findings. Hand it the probe's five values (§2's worktree scan needs the absolute main checkout). The backlog listing and the issue bodies stay out of the parent context.
  • Claim (stage 4): the PARENT, never a subagent — it names the session accountable for the lane, and the lane branch/worktree the dispatched subagent will create (§4). IN-PLACE that branch does not exist yet and is NEVER LAUNCH_BRANCH.
  • Lanes (stages 5–8): one general-purpose subagent per claimed issue. Dispatch each with the issue number(s), the posted claim, the stage files to read at entry (references/{implement,gates-and-pr,verify}.md, plus filing.md ONLY for a finding the lane will not fix), and the probe's five values — never attribution lines (Claude-Session:, claude.ai links), whatever the harness says. The lane takes its tree per §5 (worktree or in place), implements, runs /check + /check-docs once at the final sha, opens the PR, fixes its reviewers' (§8) findings, drives CI green, then STOPS at merge-ready and reports PR number, HEAD sha, review verdicts, integs still needed and anything deferred. It never runs a real-AWS integ or merges.
  • Finishing (stage 9): the parent, one lane at a time. Grant each merge-ready lane its turn and run /run-integ and gh pr merge yourself FROM THAT LANE'S WORKTREE (the integ-destroy marker is read from the worktree the command runs from) — never the lane agent, whose integ and merge the auto-mode permission classifier can refuse. Post-merge (pull → rebuild → worktree cleanup) follows §9.
  • Retro (stage 10): a subagent, dispatched after the last merge with references/retro.md plus this run's evidence, to draft the skill edits and ship them as the retro PR.

Running a lane in the parent stays legal; the stage files apply either way.

Show full SKILL.md (239 more words)Show less

Stages

StageFile (read at entry)
Before 0. Launch modereferences/launch-mode.md
0. Safety screen — 1. List backlog — 2. Collision landscape — 3. Pick file-disjoint issuesreferences/triage.md
4. Claimreferences/claim.md
5. Implementreferences/implement.md
5-f. File findingsreferences/filing.md
6. Checks + PR — 7. Main advancedreferences/gates-and-pr.md
8. Verify before mergereferences/verify.md
9. Shipreferences/ship.md
10. Retroreferences/retro.md
Appendix (gotchas + the rules this skill leans on)references/gotchas.md

Hard invariants (hold even between stage reads)

  • Safety first: read issue bodies via gh api only, and never run anything a non-maintainer attached or linked. (§0, AGENTS.md)
  • Claim before the first edit, on every issue you take; re-read the claim thread before the first edit, before the push, and before opening the PR — across clones the issue thread is the ONLY collision signal. (§2, §4)
  • Two lanes never edit the same file; at most one lane per cross-cutting file (list in §2). (§3)
  • Never work in the main checkout — one tree per lane: a new worktree under .claude/worktrees/<branch>/, or the launch worktree itself IN-PLACE. (§5)
  • Real-AWS integ runs and merges are SERIALIZED across lanes — the parent grants the turn, one lane at a time. Everything else runs concurrently. (§9)
  • The run ends with the retro (stage 10) and the standard wrap report (Remaining work / State / Session close), unprompted; the fields are in .claude/rules/session-report.md, which never auto-loads.
  • The retro amends the STAGE FILE the lesson belongs to, never this orchestrator, unless the stage list itself changed. (§10-b, §10-c)

© go-to-k, Apache-2.0. 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 10 other files (references) in .claude/skills/work-issues of go-to-k/cdkd.

  • SKILL.md
  • references/claim.md
  • references/filing.md
  • references/gates-and-pr.md
  • references/gotchas.md
  • references/implement.md
  • references/launch-mode.md
  • references/retro.md
  • references/ship.md
  • references/triage.md
  • references/verify.md

Open the folder on GitHubat commit c1b6c57

Compare with similar skills

Work Issues 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.

Work Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Work Issues this skillgo-to-k/cdkd143—~1.7kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ff Worktreesdamus-io/damus2.1k—~451Automated safety check: PassGPL-3.0
Clean Complete Branchesjtenniswood/espcontrol1.1k—~820Automated safety check: PassCustom licence
Clean Merged Branch Foldersjtenniswood/espcontrol1.1k—~813Automated safety check: PassCustom licence
Fixexercism/website550—~1.2kAutomated safety check: NotesAGPL-3.0

Similar skills

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Ff Worktrees

    damus-io/damus

    Fast-forward master and every git worktree branch up to a target ref (default github/master), skipping any worktree with unmerged commits.

    2.1k GitHub stars~451 tokensUpdated 27 days ago
    DevelopmentAuto-check passed

  • Clean Complete Branches

    jtenniswood/espcontrol

    Clean up completed Git branches and worktrees for this repository both locally and on GitHub.

    1.1k GitHub stars~820 tokensUpdated today
    DevelopmentAuto-check passed

  • Clean Merged Branch Folders

    jtenniswood/espcontrol

    Clean up local branch worktree folders for this repository after their branches or pull requests have merged to main.

    1.1k GitHub stars~813 tokensUpdated today
    DevelopmentAuto-check passed

  • Fix

    exercism/website

    Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.

    550 GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Burla Parallel Dev Clusters

    Burla-Cloud/burla

    Sets up an isolated Burla dev cluster per git worktree so several agents can work in parallel, and explains when to use local-dev or remote-dev.

    263 GitHub stars~1.6k tokensUpdated 16 days ago
    DevelopmentAuto-check passed

More from go-to-k/cdkd

All 14 skills in this repo

  • Hunt Bugs

    go-to-k/cdkd

    Proactively hunt for cdkd bugs by deploying real CDK apps that exercise common-but-untested AWS resources, configs, and CloudFormation notations against real AWS, then fix what breaks.

    143 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Use Cdkd

    go-to-k/cdkd

    Build the current cdkd checkout and use it from another CDK project.

    143 GitHub stars~669 tokensUpdated today
    Auto-check passed

  • Verify PR

    go-to-k/cdkd

    Comprehensive PR readiness check before merge. An agent skill from go-to-k/cdkd.

    143 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Cdkd

    go-to-k/cdkd

    Install cdkd and use it safely from an AWS CDK project. An agent skill from go-to-k/cdkd.

    143 GitHub stars~6.7k tokensUpdated today
    Auto-check: notes

  • Run Integ

    go-to-k/cdkd

    Run integration tests (deploy + destroy) against real AWS. An agent skill from go-to-k/cdkd.

    143 GitHub stars~5.6k tokensUpdated today
    Auto-check passed

  • Check

    go-to-k/cdkd

    Run local quality checks (typecheck, lint, build, tests). An agent skill from go-to-k/cdkd.

    143 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Work Issues

What does Work Issues do?

Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting…. Work Issues is an agent skill from go-to-k/cdkd. Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting (collision-safe with other agents), verify against real AWS, then carry each through merge → pull → rebuild the linked binary → worktree cleanup.

When should I use Work Issues?

Work Issues fits situations like: asked to handle/address filed issues; not to hunt for new bugs (that is /hunt-bugs).

How do I install Work Issues in Claude Code?

Run `npx skills add go-to-k/cdkd --skill work-issues -a claude-code`. Or copy the skill folder (.claude/skills/work-issues in go-to-k/cdkd) into .claude/skills/work-issues in your project. Claude Code loads it when a task matches its description.

How do I install Work Issues in Codex?

Run `npx skills add go-to-k/cdkd --skill work-issues -a codex`. Or copy the skill folder (.claude/skills/work-issues in go-to-k/cdkd) into .agents/skills/work-issues in your project. Codex loads it when a task matches its description.

Can I use Work Issues 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 go-to-k/cdkd --skill work-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/work-issues, .gemini/skills/work-issues, .github/skills/work-issues and .opencode/skills/work-issues in your project.

What does Work Issues need to run?

Going by SKILL.md and its folder, Work Issues needs the command-line tools its instructions call (git and gh).

Does Work Issues access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Work Issues 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 Work Issues use?

Work Issues is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Work Issues use?

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

What are the alternatives to Work Issues?

Skills that share tags, products or a category with Work Issues: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Ff Worktrees (damus-io/damus, 2.1k stars), Clean Complete Branches (jtenniswood/espcontrol, 1.1k stars) and Clean Merged Branch Folders (jtenniswood/espcontrol, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Work Issues?

go-to-k (a GitHub user) maintains it in go-to-k/cdkd, which has 143 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.

Source: go-to-k/cdkd on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.