agentleFS
dmzoneilldmzoneill/skills/jira-hygiene/SKILL.md

jira-hygiene

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Check and fix Jira issue hygiene - ensures issues have proper details, acceptance criteria, priority, labels, epic links, and formatting. Transitions New issues to Refinement when complete. Use when user says "Jira hygiene", "fix issue details", or "check AAP-XXXXX".

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Description: Must exist, ≥20 chars, proper formatting (h2., bullets, code blocks)

    line 37
  2. Distinctive:

    Acceptance criteria: Must exist, ≥10 chars

    line 38
  3. Distinctive:

    Priority: Must be set (default: Normal)

    line 39
  4. Distinctive:

    Transition: If status=New and has desc+AC+priority → ready for Refinement

    line 44
  5. Distinctive:

    If issue description contains "block":

    line 47
  6. Very specific:

    If validation.needs_input: add follow-up to state/current_work

    line 60
  7. Very specific:

    If "issue does not exist": learn_tool_fix("jira_view_issue", "issue does not exist", "Jira issue key incorrect or deleted", "Verify format …

    line 63
  8. Very specific:

    If "unauthorized" or "401": learn_tool_fix("jira_view_issue", "unauthorized", "Jira auth failed", "Check Jira credentials")

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Jira Hygiene

Validates and fixes Jira issues for quality and completeness. Resolves project/component from issue_key prefix or repo_name.

Inputs

InputTypeDefaultPurpose
issue_keystringrequiredJira issue key (e.g., AAP-12345)
repo_namestring-Repository name for component resolution
auto_fixbooltrueAutomatically fix issues where possible
auto_transitionbooltrueAuto-transition New → Refinement when ready
epic_keystring-Epic key to link issue to (e.g., AAP-50000)
story_pointsint-Story points to set
prioritystring-Priority to set (e.g., Major)

Workflow

1. Load Persona

  • persona_load(persona="developer") — Jira tools require developer persona

2. Knowledge & Known Issues

  • knowledge_query(project="automation-analytics-backend", persona="developer", section="patterns.coding") — Jira best practices
  • check_known_issues(tool_name="jira_view_issue", error_text="") — Check for known Jira failures

3. Lint & Fetch Issue

  • jira_lint(issue_key=issue_key) — Run automated quality checks
  • jira_view_issue_json(issue_key=issue_key) — Fetch full issue details

4. Validate Issue

Parse issue fields and check:

  • Description: Must exist, ≥20 chars, proper formatting (h2., bullets, code blocks)
  • Acceptance criteria: Must exist, ≥10 chars
  • Priority: Must be set (default: Normal)
  • Labels/Components: At least one required
  • Epic link: Required for stories/tasks
  • Fix version: Warn if missing
  • Story points: Required for In Progress/Review issues
  • Transition: If status=New and has desc+AC+priority → ready for Refinement

5. Flag Blocked (if applicable)

If issue description contains "block":

  • jira_block(issue_key=issue_key, reason="Blocker detected during hygiene check")

6. Auto-Fix (when auto_fix=true)

Apply fixes in order:

  • Status: jira_set_status(issue_key=issue_key, status="Refinement") — if transition_ready and auto_transition
  • Priority: jira_set_priority(issue_key=issue_key, priority=value) — if missing (or from inputs.priority)
  • Epic: jira_set_epic(issue_key=issue_key, epic_key=epic_key) — if inputs.epic_key provided
  • Story points: jira_set_story_points(issue_key=issue_key, points=points) — if inputs.story_points provided

7. Report & Memory

  • Build health score (0–100%) from validation
  • memory_session_log(action="Hygiene check on {issue_key}", details="Healthy" or "N issues found")
  • If validation.needs_input: add follow-up to state/current_work

8. Learning from Failures

  • If "issue does not exist": learn_tool_fix("jira_view_issue", "issue does not exist", "Jira issue key incorrect or deleted", "Verify format AAP-12345")
  • If "unauthorized" or "401": learn_tool_fix("jira_view_issue", "unauthorized", "Jira auth failed", "Check Jira credentials")

Output Format

## 🟢/🟡/🟠/🔴 Issue Health: X%
**Issue:** AAP-12345
**Summary:** ...
**Status:** ...
### Issues Found
- ❌ Missing acceptance criteria
### ✅ Fixed
- ✅ Priority
### ❓ Needs Your Input
**epic_link:** Story should be linked to an Epic → Please specify which Epic

Key MCP Tools

  • persona_load, jira_lint, jira_view_issue_json, jira_set_status, jira_set_priority, jira_set_epic, jira_set_story_points, jira_block, memory_session_log, learn_tool_fix, knowledge_query, check_known_issues

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.