New: 97,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

Jira Bugfix

by sillsdev in sillsdev/FieldWorks

End-to-end JIRA bugfix workflow: fetch issue, assign, branch, TDD, fix, test, update AGENTS.md, commit, PR, and update JIRA.

MITAuto-check passedTesting & QA

Install Jira Bugfix

skills CLI
$ npx skills add sillsdev/FieldWorks --skill jira-bugfix -a claude-code

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

GitHub CLI
$ gh skill install sillsdev/FieldWorks jira-bugfix --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/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/jira-bugfix .claude/skills/jira-bugfix && 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
jira-bugfix
GitHub stars
110
Token cost
~1.1k tokens
SKILL.md length
620 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

End-to-end JIRA bugfix workflow: fetch issue, assign, branch, TDD, fix, test, update AGENTS.md, commit, PR, and update JIRA.

  • Works in 2 steps: TDD, and the escape hatch → Devil's advocate
  • The user says fix LT-XXXXX
  • SKILL.md covers Steps, Step 3 -- TDD, and the escape…, Step 6 -- Devil's advocate and Branching and worktrees, plus 4 more sections
  • Calls git

What it does

Jira Bugfix is an agent skill from sillsdev/FieldWorks. End-to-end JIRA bugfix workflow: fetch issue, assign, branch, TDD, fix, test, update AGENTS.md, commit, PR, and update JIRA. Use when the user says "fix LT-XXXXX" or references a JIRA bug to resolve.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires atlassian-skills, atlassian-readonly-skills.

It sits in Testing & QA, covering Test-driven development and Agent instruction files. It works with Jira. The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts. The licence is MIT.

When your agent uses it

  • The user says fix LT-XXXXX
  • References a JIRA bug to resolve

Example prompts

  • “fix LT-XXXXX”
  • “/jira-bugfix”

Requirements

  • Compatibility (from SKILL.md): Requires atlassian-skills, atlassian-readonly-skills.

Workflow steps

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

  1. TDD, and the escape hatch
  2. Devil's advocate

What it can do on your machine

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

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

  • Network

    No URLs in SKILL.md. Its commands use 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.

  • Compatibility

    Requires atlassian-skills, atlassian-readonly-skills.

    From compatibility in the SKILL.md frontmatter.

Context cost

Jira Bugfix loads about 1.1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 620 words of instructions outside code blocks.

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

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 sillsdev/FieldWorks at commit 44b1d04, republished under its MIT licence (© sillsdev). 620 words, ~1,145 tokens.

Download SKILL.mdSave it as .claude/skills/jira-bugfix/SKILL.md (or your agent's skills folder).
name
jira-bugfix
description
End-to-end JIRA bugfix workflow: fetch issue, assign, branch, TDD, fix, test, update AGENTS.md, commit, PR, and update JIRA. Use when the user says "fix LT-XXXXX" or references a JIRA bug to resolve.
compatibility
Requires atlassian-skills, atlassian-readonly-skills.
license
MIT
metadata.author
FieldWorks team
metadata.version
2.0

JIRA Bugfix

Fixing a bug sourced from an LT ticket, from triage to PR.

Tell the user the steps before starting, then work them in order. Pause at the four decision points below; everything else proceeds.

Steps

#StepNotes
0Fetch the issueSummary, status, components, comments. Comments often carry the repro
1Assign, move to In ProgressSkip if already there
2BranchLT-XXXXX-short-slug off fresh origin/main
3Reproduce with a failing testThe most important step. See below
4FixThe minimal change that makes the test pass
5Widen coverageEdge cases, other call sites of the changed code, backward compatibility
6Devil's advocateChallenge the fix and the tests before anyone else does
7AGENTS.mdUpdate only if a contract or behaviour documented there changed
8Commitcommit-messages skill. gitlint runs in CI
9PRpr-preflight -- the required entrypoint. Never hand-write a PR body
10Comment on the ticketRoot cause, fix, PR link, tests added

Arriving from jira-issue? If that skill just filed the ticket and the user chose "start now", steps 0-2 are already done -- the issue is fetched, assigned, In Progress, and the branch and worktree are named in a ticket comment. Begin at step 3.

Step 3 -- TDD, and the escape hatch

Write a failing test that captures the bug before writing any fix. Name it MethodName_Scenario_ExpectedBehavior. Confirm it fails, then fix, then confirm it passes.

powershell
.\test.ps1 -TestFilter "Name~TestMethodName" -CommentHygiene

A filter that matches nothing still exits 0 and prints PASS. Check Total tests: N is greater than zero.

If a test is genuinely impossible -- purely visual, needs an external service, or lives in build/packaging -- say which of those it is, then ask whether to proceed without one. Do not skip silently, and do not invent a test that passes either way.

Step 6 -- Devil's advocate

Before finalising, argue against your own work:

  • Is there a simpler or more robust fix? If several are reasonable, present them with trade-offs and let the user choose.
  • Does it regress anything, or change performance or compatibility?
  • Is the scope right -- not so narrow it misses sibling cases, not so broad it becomes a refactor?
  • Does the diff carry dead code, debug artefacts, or stray whitespace?

Surface any uncertainty to the user rather than resolving it silently.

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

Branching and worktrees

LT-XXXXX-short-slug, for example LT-22715-nc-delete-warning. The number keeps step 2's "contains the LT number" check working and makes the branch greppable; the slug is what makes a list of a dozen worktrees readable.

Do not create a worktree without asking -- and do not refuse to create one either. scripts/Worktree-CreateFromBranch.ps1 and the Worktree: VS Code tasks exist. If .claude/.jira-issue-prefs.json records a workspace preference, follow it and say so. The script decides where worktrees go -- read it rather than trusting a path written here, and match what git worktree list already shows.

JIRA mechanics

All of it -- create, comment, attach, link, transition, and the custom_fields back doors for assignee and Affects Version -- is in .claude/skills/jira-issue/references/publish.md. Do not duplicate it here.

Never transition to Done or Resolved. That follows a merged PR, and it is not this skill's call.

Pause for the user

  1. The current branch does not match the ticket.
  2. A failing test cannot be written.
  3. Devil's advocate surfaced a real alternative or uncertainty.
  4. The fix reveals a larger problem than the ticket describes.

When things fail

  • JIRA unreachable -- ask for the details, carry on, update the ticket at the end.
  • Tests fail after the fix -- show the failures and ask; do not tune the test to pass.
  • Push rejected -- pull with rebase, resolve, retry.

Composes with

jira-issue (files the ticket, hands off here at step 3) · atlassian-skills (JIRA writes) · commit-messages (step 8) · pr-preflight (step 9) · fieldworks-test-coverage (step 5)

© sillsdev, 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/jira-bugfix of sillsdev/FieldWorks.

Open the folder on GitHubat commit 44b1d04

Compare with similar skills

Jira Bugfix 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.

Jira Bugfix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jira Bugfix this skillsillsdev/FieldWorks110—~1.1kAutomated safety check: PassMIT
Et TDDFlameskyDexive/Legends-Of-Heroes929—~243Automated safety check: PassMIT
Go Rigmudrii/openclaw-dashboard457—~2.8kAutomated safety check: PassMIT
Go Rigmudrii/openclaw-dashboard457—~682Automated safety check: PassMIT
Py Rigmudrii/hermesd119—~6.3kAutomated safety check: PassMIT
TDDfossasia/eventyay-interpretation1.6k28 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Et TDD

    FlameskyDexive/Legends-Of-Heroes

    ET test-driven development workflow for WOW. An agent skill from FlameskyDexive/Legends-Of-Heroes.

    929 GitHub stars~243 tokensUpdated 15 days ago
    Testing & QAAuto-check passed

  • Go Rig

    mudrii/openclaw-dashboard

    A skill your agent uses when building, reviewing, or refactoring Go code that must follow strict design discipline — ATDD/TDD workflow, explicit dependency injection, package-boundary discipline…

    457 GitHub stars~2.8k tokensUpdated 14 days ago
    DevelopmentAuto-check passed

  • Go Rig

    mudrii/openclaw-dashboard

    A skill your agent uses when building, reviewing, or refactoring Go code in this repository.

    457 GitHub stars~682 tokensUpdated 14 days ago
    DevelopmentAuto-check passed

  • Py Rig

    mudrii/hermesd

    A skill your agent uses when building, reviewing, or refactoring Python code that requires strong maintainability discipline: SRP, DRY, OCP, explicit dependency injection, TDD/ATDD workflow, strict…

    119 GitHub stars~6.3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

More from sillsdev/FieldWorks

All 29 skills in this repo

  • Atlassian Readonly Skills

    sillsdev/FieldWorks

    Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.

    110 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Atlassian Skills

    sillsdev/FieldWorks

    Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.

    110 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Fieldworks Winapp

    sillsdev/FieldWorks

    Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.

    110 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Convert Slice

    sillsdev/FieldWorks

    Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.

    110 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Dependabot Consolidation

    sillsdev/FieldWorks

    Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…

    110 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed

  • Fieldworks Semantic Render Parity

    sillsdev/FieldWorks

    Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.

    110 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Jira Bugfix

What does Jira Bugfix do?

End-to-end JIRA bugfix workflow: fetch issue, assign, branch, TDD, fix, test, update AGENTS.md, commit, PR, and update JIRA. Jira Bugfix is an agent skill from sillsdev/FieldWorks.md, commit, PR, and update JIRA.

When should I use Jira Bugfix?

Jira Bugfix fits situations like: the user says fix LT-XXXXX; references a JIRA bug to resolve.

How do I install Jira Bugfix in Claude Code?

Run `npx skills add sillsdev/FieldWorks --skill jira-bugfix -a claude-code`. Or copy the skill folder (.claude/skills/jira-bugfix in sillsdev/FieldWorks) into .claude/skills/jira-bugfix in your project. Claude Code loads it when a task matches its description.

How do I install Jira Bugfix in Codex?

Run `npx skills add sillsdev/FieldWorks --skill jira-bugfix -a codex`. Or copy the skill folder (.claude/skills/jira-bugfix in sillsdev/FieldWorks) into .agents/skills/jira-bugfix in your project. Codex loads it when a task matches its description.

Can I use Jira Bugfix 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 sillsdev/FieldWorks --skill jira-bugfix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira-bugfix, .gemini/skills/jira-bugfix, .github/skills/jira-bugfix and .opencode/skills/jira-bugfix in your project.

What does Jira Bugfix need to run?

Going by SKILL.md and its folder, Jira Bugfix needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): Requires atlassian-skills, atlassian-readonly-skills..

Does Jira Bugfix access the network?

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

Is Jira Bugfix 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 Jira Bugfix use?

Jira Bugfix is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jira Bugfix use?

About 1.1k tokens (SKILL.md is roughly 4.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 Jira Bugfix?

Skills that share tags, products or a category with Jira Bugfix: Et TDD (FlameskyDexive/Legends-Of-Heroes, 929 stars), Go Rig (mudrii/openclaw-dashboard, 457 stars), Go Rig (mudrii/openclaw-dashboard, 457 stars) and Py Rig (mudrii/hermesd, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jira Bugfix?

sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

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