agentleFS
alanalvestechalanalvestech/hitank/skills/jira/SKILL.md

jira

Skill38 starsChanged 8 months agoMITView on GitHub

Manage Jira issues, projects, sprints and boards via REST API

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use confluence, meet and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SpillwaveSolutionsSkill

    confluence

    Manage Confluence documentation with downloads, uploads, conversions, and diagrams. Use when asked to "download Confluence pages", "upload to Confluence", "convert Wiki Markup", "sync markdown to Confluence", "create Confluence page", or "handle Confluence images".

    Also in 9 projects that use this

  • kv0906Skill

    meet

    Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.

    Also in 3 projects that use this

  • er1chuSkill

    monday

    Full Monday morning setup. Creates week folder, pulls carry-forward, and generates briefing in one pass. Use on Monday mornings or when the user says "monday", "start my week", or "monday morning".

    Also in 3 projects that use this

  • koderoverSkill

    jenkins

    Jenkins CI/CD 操作。用于:(1) 触发 Jenkins 任务构建 (2) 查询任务状态和构建历史 (3) 获取构建日志 (4) 操作 Jenkins 节点和配置

    Also in 3 projects that use this

  • refly-aiSkill

    asana

    Integrate with Asana for task management. Use when you need to: (1) create and manage Asana tasks, (2) organize project work, or (3) automate team task tracking workflows.

    Also in 3 projects that use this

  • montymiSkill

    tech-spec

    Parse and review Technical Specification documents for completeness, consistency, and implementation readiness

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 2

    Distinctive

    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 the output is OK, proceed to the Flow section.

    line 40
  2. Very specific:

    If the output is SETUP_NEEDED, guide the user step by step.

    line 42
  3. Distinctive:

    If the script outputs an error, the config is invalid.

    line 65
  4. Distinctive:

    Ask the user to confirm the details before creating.

    line 104

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “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

Connect to Jira Cloud to manage projects, issues, sprints, boards and more. Pure Ruby, zero gems — stdlib only.

Structure

scripts/
├── auth.rb          # Basic Auth + jira_request helper (required by all scripts)
├── check_setup.rb   # Check if config exists (outputs OK or SETUP_NEEDED)
├── save_config.rb   # Save and validate domain, email and API token
├── projects.rb      # List projects
├── project.rb       # Get project details
├── issues.rb        # Search issues using JQL
├── issue.rb         # Get issue details
├── create_issue.rb  # Create an issue
├── update_issue.rb  # Update an issue
├── transitions.rb   # List available transitions for an issue
├── transition.rb    # Transition an issue (change status)
├── comments.rb      # List comments on an issue
├── add_comment.rb   # Add a comment to an issue
├── assign.rb        # Assign an issue to a user
├── boards.rb        # List boards (Agile)
└── sprints.rb       # List sprints for a board

Setup (check before using)

ruby ~/.claude/skills/jira/scripts/check_setup.rb

If the output is OK, proceed to the Flow section.

If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.

Step 1 — Ask the user for their Jira domain:

What is your Jira Cloud domain? For example, if you access Jira at https://mycompany.atlassian.net, the domain is mycompany.

Step 2 — Ask the user to create an API token:

Create an API token at: https://id.atlassian.com/manage-profile/security/api-tokens

Click Create API token, give it a name (e.g. "hitank"), and copy the token. Also confirm your Atlassian account email.

Paste the email and token here.

Step 3 — When the user provides all three values, save them:

ruby ~/.claude/skills/jira/scripts/save_config.rb 'DOMAIN' 'EMAIL' 'TOKEN'

If the script outputs an error, the config is invalid. Ask the user to double-check and try again.

If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.

Flow

The argument $ARGUMENTS may contain a project key or issue key.

Step 1: List projects

ruby ~/.claude/skills/jira/scripts/projects.rb

Present the projects. If $ARGUMENTS matches a project key, use that project. Otherwise ask which project to work with.

Step 2: Search issues

ruby ~/.claude/skills/jira/scripts/issues.rb 'project = PROJECT_KEY ORDER BY updated DESC'

Present the issues and ask what the user wants to do.

Step 3: Actions

Get issue details:

ruby ~/.claude/skills/jira/scripts/issue.rb ISSUE_KEY

Search with JQL:

ruby ~/.claude/skills/jira/scripts/issues.rb 'project = MYPROJ AND status = "In Progress"'
ruby ~/.claude/skills/jira/scripts/issues.rb 'assignee = currentUser() ORDER BY priority DESC' --max 50

Create an issue (requires user confirmation):

Ask the user to confirm the details before creating.

ruby ~/.claude/skills/jira/scripts/create_issue.rb PROJECT_KEY "Issue summary"
ruby ~/.claude/skills/jira/scripts/create_issue.rb PROJECT_KEY "Fix login bug" --type Bug --priority High --description "Detailed description"

Update an issue (requires user confirmation):

Show current issue details first, then ask what to change.

ruby ~/.claude/skills/jira/scripts/update_issue.rb ISSUE_KEY '{"summary":"New title","priority":{"name":"High"}}'

Transition an issue (requires user confirmation):

First list available transitions, then ask which one to apply.

ruby ~/.claude/skills/jira/scripts/transitions.rb ISSUE_KEY
ruby ~/.claude/skills/jira/scripts/transition.rb ISSUE_KEY TRANSITION_ID

Assign an issue (requires user confirmation):

ruby ~/.claude/skills/jira/scripts/assign.rb ISSUE_KEY ACCOUNT_ID
ruby ~/.claude/skills/jira/scripts/assign.rb ISSUE_KEY unassign

List comments:

ruby ~/.claude/skills/jira/scripts/comments.rb ISSUE_KEY

Add a comment (requires user confirmation):

ruby ~/.claude/skills/jira/scripts/add_comment.rb ISSUE_KEY "Comment text here"

List boards (Agile):

ruby ~/.claude/skills/jira/scripts/boards.rb

List sprints:

ruby ~/.claude/skills/jira/scripts/sprints.rb BOARD_ID
ruby ~/.claude/skills/jira/scripts/sprints.rb BOARD_ID --state active

Notes

  • Pure Ruby, zero gems — stdlib only (json, net/http, uri, base64, fileutils)
  • Auth via Basic Auth (email + API token)
  • Config file: ~/.config/jira/config.json (outside the repo, never commit)
  • Creating, updating, transitioning, and assigning issues require explicit user confirmation
  • Adding comments requires user confirmation
  • Jira Cloud API v3 uses Atlassian Document Format (ADF) for descriptions and comments
  • JQL (Jira Query Language) is used for searching issues
  • Base URL: https://DOMAIN.atlassian.net/rest/api/3
  • Agile URL: https://DOMAIN.atlassian.net/rest/agile/1.0

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.