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".
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
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
- Distinctive: line 37
Description: Must exist, ≥20 chars, proper formatting (h2., bullets, code blocks)
- Distinctive: line 38
Acceptance criteria: Must exist, ≥10 chars
- Distinctive: line 39
Priority: Must be set (default: Normal)
- Distinctive: line 44
Transition: If status=New and has desc+AC+priority → ready for Refinement
- Distinctive: line 47
If issue description contains "block":
- Very specific: line 60
If validation.needs_input: add follow-up to state/current_work
- Very specific: line 63
If "issue does not exist": learn_tool_fix("jira_view_issue", "issue does not exist", "Jira issue key incorrect or deleted", "Verify format …
- Very specific: line 64
If "unauthorized" or "401": learn_tool_fix("jira_view_issue", "unauthorized", "Jira auth failed", "Check Jira credentials")
≈ “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.
Files
Jira Hygiene
Validates and fixes Jira issues for quality and completeness. Resolves project/component from issue_key prefix or repo_name.
Inputs
| Input | Type | Default | Purpose |
issue_key | string | required | Jira issue key (e.g., AAP-12345) |
repo_name | string | - | Repository name for component resolution |
auto_fix | bool | true | Automatically fix issues where possible |
auto_transition | bool | true | Auto-transition New → Refinement when ready |
epic_key | string | - | Epic key to link issue to (e.g., AAP-50000) |
story_points | int | - | Story points to set |
priority | string | - | 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 practicescheck_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 checksjira_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 EpicKey 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
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
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.

