agentleFS
dmzoneilldmzoneill/skills/clone-jira-issue/SKILL.md

clone-jira-issue

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Clone a Jira issue for similar work. Clones issue, links to original, assigns to current user. Use when user says "clone issue", "duplicate issue", or "copy AAP-XXXXX".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If assign_to_me: jira_assign(issue_key=new_key)

    line 43
  2. Very specific:

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

    line 56

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

Clone Jira Issue

Clones an existing issue for similar work. Links clone to original and optionally assigns to current user.

Inputs

InputTypeDefaultPurpose
issue_keystringrequiredSource issue key (e.g., AAP-12345)
new_summarystring""New summary (defaults to "Clone of {original}")
link_typestringrelates torelates to, blocks, is blocked by
assign_to_mebooltrueAssign cloned issue to current user

Workflow

1. Load Persona

  • persona_load(persona="developer")

2. Known Issues

  • check_known_issues(tool_name="jira", error_text="")
  • check_known_issues(tool_name="clone", error_text="")

3. Get Source Issue

  • jira_view_issue(issue_key=issue_key) — Fetch source details
  • Parse: extract summary, type; verify exists (len > 50)

4. Clone Issue

  • jira_clone_issue(issue_key=issue_key, summary=new_summary or "Clone: " + source_summary)
  • Parse result: extract new_key (AAP-XXXXX pattern)

5. Link & Assign

  • jira_add_link(from_issue=new_key, to_issue=issue_key, link_type=link_type) — Link clone to original
  • If assign_to_me: jira_assign(issue_key=new_key)

6. Run Hygiene on Clone

  • skill_run(skill_name="jira_hygiene", inputs='{"issue_key": "' + new_key + '", "auto_fix": true, "auto_transition": false}')

7. Memory

  • memory_session_log(action="Cloned {issue_key} to {new_key}")
  • memory_append(key="state/current_work", list_path="active_issues", item={key: new_key, status: New, cloned_from: issue_key})

8. Learning from Failures

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

Output Format

## 📋 Clone Issue: AAP-12345

### ✅ Issue Cloned Successfully

**Original:** AAP-12345
**Clone:** AAP-12346
**Summary:** Clone: Fix auth bug

### Actions Taken

- ✅ Created AAP-12346
- ✅ Linked to AAP-12345 (relates to)
- ✅ Assigned to you

### Next Steps

- jira_view_issue(issue_key='AAP-12346')
- skill_run('start_work', '{"issue_key": "AAP-12346"}')

Key MCP Tools

  • persona_load, jira_view_issue, jira_clone_issue, jira_add_link, jira_assign, skill_run, memory_session_log, memory_append, learn_tool_fix, 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.