agentleFS
Sign inStart free
claudio-atilano-uviclaudio-atilano-uvi/claude-skills/plan-to-jira/SKILL.md

plan-to-jira

Skill0 starsChanged 4 months agoMITView on GitHub

Post implementation plans to Jira tickets as formatted comments. Trigger when: a plan file is finalized during plan mode and needs to be posted to Jira, user says "post plan to jira", "post plan to ticket", "update ticket with plan", or after exiting plan mode when the branch contains a Jira ticket key. Also trigger for: "sync plan to jira", "add plan as comment".

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 no ticket key is specified, the script extracts it from the current git branch name:

    line 18
  2. Distinctive:

    When a plan is finalized (plan mode exits with approval), locate the plan file.

    line 49
  3. Distinctive:

    Run the helper script to post the plan as a comment.

    line 51

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

Plan to Jira

Posts a markdown plan file as a formatted Jira comment. Converts markdown (headings, tables, lists, code blocks, bold, inline code, links) to Atlassian Document Format (ADF).

Ticket Resolution

If no ticket key is specified, the script extracts it from the current git branch name:

  • feat/SCA-41 → SCA-41
  • bugfix/GP-123-fix-auth → GP-123
  • SCA-99-add-feature → SCA-99

Helper Script

.claude/skills/plan-to-jira/scripts/plan-to-jira --help

Post a plan file

.claude/skills/plan-to-jira/scripts/plan-to-jira path/to/plan.md

Override ticket key

.claude/skills/plan-to-jira/scripts/plan-to-jira path/to/plan.md --ticket SCA-41

Dry run (print ADF without posting)

.claude/skills/plan-to-jira/scripts/plan-to-jira path/to/plan.md --dry-run

Workflow

  1. When a plan is finalized (plan mode exits with approval), locate the plan file.
  2. Determine the Jira ticket key from the branch name or ask the user.
  3. Run the helper script to post the plan as a comment.
  4. Report the ticket URL to the user.

Requirements

  • Credentials in ~/.claude-skills/.env (same as the jira skill: JIRA_EMAIL, JIRA_API_TOKEN)
  • Git repo with a branch containing a Jira ticket key (or use --ticket)

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