agentleFS
Sign inStart free
freemafreema/ai-skills/skills/jira/SKILL.md

jira

Skill5 starsChanged 20 days agoMITView on GitHub

Post code review verdicts to Jira. Use after a code review is done and the user wants to sync the result to Jira. Triggers on: "post to Jira", "update the ticket", "sync review to Jira", or when a review is complete and Jira context is available (project key, issue number, or Atlassian MCP connected). Posts a concise verdict comment, flags blockers, and suggests workflow transitions.

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 10 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

  • refly-aiSkill

    hubspot

    Integrate with HubSpot for CRM management. Use when you need to: (1) manage contacts and deals, (2) track sales pipelines, or (3) automate marketing and CRM workflows.

    Also in 4 projects that use this

  • koderoverSkill

    jenkins

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

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 5

    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:

    After a code review is complete (use the code-review skill first)

    line 19
  2. Distinctive:

    When the user explicitly asks to post/sync the review to Jira

    line 20
  3. Distinctive:

    When Jira context is available: project key, issue number, branch name, or Atlassian MCP connected

    line 21
  4. Distinctive:

    Suggest next transition: if no blockers (e.g., "Ready for QA")

    line 30
  5. Distinctive:

    Blocker found?: Add sub-task or comment with the fix description

    line 48
  6. Distinctive:

    No Jira issue found?: Ask the user for the issue key.

    line 56
  7. Very specific:

    No review done yet?: Run the code-review skill first, then come back here.

    line 57

“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 Review Sync

Post a concise code review verdict to the relevant Jira issue after a PR/MR review.

When to Use

  • After a code review is complete (use the code-review skill first)
  • When the user explicitly asks to post/sync the review to Jira
  • When Jira context is available: project key, issue number, branch name, or Atlassian MCP connected

Workflow

  1. Find the issue — search by MR/PR title or branch name if not provided directly
  2. Post the verdict as a Jira comment (short summary, not the full review)
  3. Flag blockers explicitly in the comment
  4. Suggest next transition if no blockers (e.g., "Ready for QA")

Jira Comment Template

Code Review: [MR/PR title]
Approach: [one sentence on what's solid]
Blocker: [blocker description + fix] / No blockers found
Minor notes: [count] (details in MR)
Verdict: [Ready to merge after fix / Approved / Needs rework]

Actions After Posting

  • Blocker found? Add sub-task or comment with the fix description
  • No blockers? Suggest transitioning the issue to the next workflow state
  • Multiple blockers? List all of them in the comment — don't split across sub-tasks

Edge Cases

  • No Jira issue found? Ask the user for the issue key. Don't guess.
  • No review done yet? Run the code-review skill first, then come back here.
  • No Atlassian MCP connected? Output the comment template for the user to paste manually.

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