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 Issue

by joesaby in joesaby/astro-mermaid

End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth.

MITAuto-check passedDevelopment

Install Work Issue

skills CLI
$ npx skills add joesaby/astro-mermaid --skill work-issue -a claude-code

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

GitHub CLI
$ gh skill install joesaby/astro-mermaid work-issue --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/joesaby/astro-mermaid.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/work-issue .claude/skills/work-issue && 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-issue
GitHub stars
123
Token cost
~891 tokens
SKILL.md length
454 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth.

  • Works in 9 steps: Load context → Triage into a tier → Brainstorm (Subtle tier only) → …
  • The user says work issue N
  • SKILL.md covers Step 0 — Load context, Step 1 — Triage into a tier, Step 2 — Brainstorm (Subtle… and Step 3 — TDD (Standard + Subtle), plus 6 more sections
  • Calls gh, npm and git

What it does

Work Issue is an agent skill from joesaby/astro-mermaid. End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth. Use when the user says "work issue N", "fix issue N", "/work-issue N", or asks to resolve a GitHub issue/PR in this repo.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Diagrams, Static sites and blogs and Brainstorming. It works with Astro, Mermaid and GitHub. The repository describes itself as: Mermaid integration using pattern from cloudflare-docs. The licence is MIT.

When your agent uses it

  • The user says work issue N
  • Asks to resolve a GitHub issue/PR in this repo

Example prompts

  • “work issue N”
  • “fix issue N”
  • “/work-issue N”
  • “/work-issue”

Workflow steps

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

  1. Load context
  2. Triage into a tier
  3. Brainstorm (Subtle tier only)
  4. TDD (Standard + Subtle)
  5. Implement
  6. Spec & docs update
  7. Verify in a demo (when user-visible)
  8. Code review (Standard + Subtle)
  9. Commit & push

What it can do on your machine

Read from SKILL.md and the folder at commit ce85c02. 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
    • npm
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use gh, npm and git, 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 Issue loads about 891 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 454 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~891

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 joesaby/astro-mermaid at commit ce85c02, republished under its MIT licence (© joesaby). 454 words, ~891 tokens.

Download SKILL.mdSave it as .claude/skills/work-issue/SKILL.md (or your agent's skills folder).
name
work-issue
description
End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth. Use when the user says "work issue N", "fix issue N", "/work-issue N", or asks to resolve a GitHub issue/PR in this repo.

Work an Issue

Resolve a GitHub issue for astro-mermaid with ceremony scaled to its complexity. Two phases — triage, then execute the tier.

The argument is an issue number (or PR number). If none is given, ask which issue.

Step 0 — Load context

  • gh issue view <n> (or gh pr view <n>) — read the full body and comments.
  • Read AGENTS.md, astro-mermaid-integration.js, astro-mermaid-integration.d.ts.
  • Create a branch: git checkout -b fix/issue-<n>-<slug> (use feat/ for features). Never work on main.

Step 1 — Triage into a tier

Classify the issue, then state the tier to the user before proceeding:

  • Trivial — typo, dep bump, doc-only, copy fix. → Skip to "Implement" + "Verify". No subagents.
  • Standard — a contained bug or feature with clear scope. → TDD → implement → docs → one code-reviewer subagent.
  • Subtle — touches client serialization/security, the public config API, or has multiple viable approaches (the #18 class). → Full pipeline including the brainstorm subagent and an adversarial review.

When unsure, round up a tier.

Step 2 — Brainstorm (Subtle tier only)

Spawn the brainstorm subagent (Agent tool, subagent_type: "brainstorm") with the issue text. Wait for its ranked approaches. Pick one, tell the user which and why. Do not skip this for security/API issues — it exists to stop naive fixes (see #18).

Step 3 — TDD (Standard + Subtle)

Write the failing test FIRST in test/ (vitest). It must encode the regression that motivated the issue — i.e. it fails on origin/main and passes after the fix. Run npm test and confirm the new test fails for the right reason before implementing.

Step 4 — Implement

Make the change in astro-mermaid-integration.js (and .d.ts if the public API changes). Honor the hard rules in AGENTS.md — especially: never serialize user functions to the client. Run npm test until green.

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

Step 5 — Spec & docs update

If the public API or behavior changed, update in the same commit:

  • astro-mermaid-integration.d.ts (types)
  • README.md and docs/API.md
  • CHANGELOG.md → [Unreleased] Skip only for genuinely internal changes.

Step 6 — Verify in a demo (when user-visible)

If the change affects rendering, add/adjust an example in a demo's content and confirm it renders (the verify or run skill, or a quick Playwright check). Refresh the stale file:.. copy first: cp astro-mermaid-integration.js astro-mermaid-integration.d.ts <demo>/node_modules/astro-mermaid/.

Step 7 — Code review (Standard + Subtle)

Spawn the code-reviewer subagent (subagent_type: "code-reviewer") on the diff. Address every blocking finding (re-run review if needed). Report nits to the user.

Step 8 — Commit & push

  • Conventional Commits — fix: for bugs, feat: for features. Reference the issue (fixes #<n>).
  • End the commit body with the Co-Authored-By trailer.
  • Push the branch. Tell the user the branch is up and offer to open/update the PR (gh pr create).

Notes

  • Never edit version in package.json — semantic-release owns it.
  • docs:/chore:/test: commits do not trigger a release; a fix:/feat: must carry the user-facing change for it to ship.

© joesaby, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/work-issue of joesaby/astro-mermaid.

Open the folder on GitHubat commit ce85c02

Compare with similar skills

Work Issue 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 Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Work Issue this skilljoesaby/astro-mermaid123—~891Automated safety check: PassMIT
Audit Flowzebbern/claude-code-guide4.7k—~4.2kAutomated safety check: PassMIT
Mind Mapmohitagw15856/pm-claude-skills1.4k—~710Automated safety check: PassMIT
GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram18k—~427Automated safety check: PassMIT
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid1751 repos~5.6kAutomated safety check: PassNone
GitDiagram Repo Architectureahmedkhaleel2004/gitdiagram18k—~429Automated safety check: PassMIT

Similar skills

  • Audit Flow

    zebbern/claude-code-guide

    Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export.

    4.7k GitHub stars~4.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Mind Map

    mohitagw15856/pm-claude-skills

    Turn a topic, brainstorm, or document into a structured mind map.

    1.4k GitHub stars~710 tokensUpdated today
    DevelopmentAuto-check passed

  • GitDiagram Repository Overview

    ahmedkhaleel2004/gitdiagram

    Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.

    18k GitHub stars~427 tokensUpdated today
    DevelopmentAuto-check passed

  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    175 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed

  • GitDiagram Repo Architecture

    ahmedkhaleel2004/gitdiagram

    Explains how a public GitHub repository is built by fetching its GitDiagram architecture diagram, components and optional explainer video.

    18k GitHub stars~429 tokensUpdated today
    DevelopmentAuto-check passed

  • Astro Code Review

    withastro/astro

    Official

    Perform a static, read-only code review of an Astro pull request or of a local branch, commit range, diff, patch, or working tree being prepared as a pull request.

    63k GitHub stars~7.6k tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Work Issue

What does Work Issue do?

End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth. Work Issue is an agent skill from joesaby/astro-mermaid. End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth.

When should I use Work Issue?

Work Issue fits situations like: the user says work issue N; asks to resolve a GitHub issue/PR in this repo.

How do I install Work Issue in Claude Code?

Run `npx skills add joesaby/astro-mermaid --skill work-issue -a claude-code`. Or copy the skill folder (.claude/skills/work-issue in joesaby/astro-mermaid) into .claude/skills/work-issue in your project. Claude Code loads it when a task matches its description.

How do I install Work Issue in Codex?

Run `npx skills add joesaby/astro-mermaid --skill work-issue -a codex`. Or copy the skill folder (.claude/skills/work-issue in joesaby/astro-mermaid) into .agents/skills/work-issue in your project. Codex loads it when a task matches its description.

Can I use Work Issue 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 joesaby/astro-mermaid --skill work-issue -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-issue, .gemini/skills/work-issue, .github/skills/work-issue and .opencode/skills/work-issue in your project.

What does Work Issue need to run?

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

Does Work Issue access the network?

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

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

Work Issue 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 Work Issue use?

About 891 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Work Issue?

Skills that share tags, products or a category with Work Issue: Audit Flow (zebbern/claude-code-guide, 4.7k stars), Mind Map (mohitagw15856/pm-claude-skills, 1.4k stars), GitDiagram Repository Overview (ahmedkhaleel2004/gitdiagram, 18k stars) and Design Doc Mermaid (SpillwaveSolutions/design-doc-mermaid, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Work Issue?

joesaby (a GitHub user) maintains it in joesaby/astro-mermaid, which has 123 GitHub stars. The repository was last updated on July 21, 2026.

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