agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/jira-hygiene-all/SKILL.md

jira-hygiene-all

Skill2 starsChanged 20 days agoApache-2.0View on GitHub

Run hygiene checks on all your assigned Jira issues. Fetches all issues assigned to you and runs jira_hygiene on each. Use when user says "hygiene all", "check all my issues", or "scheduled cleanup".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If dry_run: note "Mode: 🔍 Dry Run (no changes made)"

    line 37

≈ “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 All

Batch hygiene checks on all assigned Jira issues. Useful for nightly backlog cleanup.

Inputs

InputTypeDefaultPurpose
statusstring""Filter by status (e.g., "In Progress", "New"). Empty = all
limitint200Max issues to process
auto_fixbooltrueAuto-fix where possible
auto_transitionbooltrueAuto-transition New → Refinement
dry_runboolfalseShow what would be fixed without making changes

Workflow

1. Load Persona

  • persona_load(persona="developer")

2. Fetch My Issues

  • jira_my_issues(status=status) — Get all issues assigned to user
  • Parse output: extract issue keys (AAP-XXXXX pattern), deduplicate, apply limit

3. Run Hygiene on Each

For each issue_key in parsed list:

  • skill_run(skill_name="jira_hygiene", inputs='{"issue_key": "' + issue_key + '", "auto_fix": ' + str(auto_fix and not dry_run).lower() + ', "auto_transition": ' + str(auto_transition and not dry_run).lower() + '}')
  • Categorize result: healthy (100%), fixed, needs_attention, error

4. Build Summary

  • Count: healthy, fixed, needs_attention
  • List MRs needing attention (first 10) with links
  • If dry_run: note "Mode: 🔍 Dry Run (no changes made)"

5. Log Session

  • memory_session_log(action="Batch Jira hygiene on N issues", details="Healthy: X, Fixed: Y, Needs attention: Z")

Output Format

## 🧹 Batch Jira Hygiene Report

**Issues Found:** N
**Processed:** N
**Mode:** 🔍 Dry Run (if applicable)

### Summary
- ✅ **Healthy:** N
- 🔧 **Fixed:** N
- ⚠️ **Needs Attention:** N

### ⚠️ Issues Needing Manual Attention
- [AAP-12345](https://issues.redhat.com/browse/AAP-12345)
### Details
- ✅ AAP-12345 (100%)
- 🔧 AAP-12346 (fixed)
- ⚠️ AAP-12347 (50%)

Quick Actions (in output)

skill_run("jira_hygiene", '{"issue_key": "AAP-12345"}')
skill_run("jira_hygiene_all", '{}')

Key MCP Tools

  • persona_load, jira_my_issues, skill_run, memory_session_log

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.

Check your setup, free