jira

Post code review verdicts and flag blockers to Jira tickets after a review completes.

3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/freema/ai-skills --skill jira-freema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/freema/ai-skills/tree/main/skills/jira
Command: npx skills add https://github.com/freema/ai-skills --skill jira-freema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post code review verdicts to Jira after a code review, enabling teams to keep Jira tickets in sync with review outcomes.

Core Features & Use Cases

  • Post a concise verdict comment to the Jira issue after a review completes.
  • Flag blockers explicitly in the Jira issue and suggest appropriate workflow transitions (e.g., Ready for QA, Needs Rework).
  • Works when Jira context (project key, issue number, or Atlassian MCP connection) is available.

Quick Start

After finishing a code review, instruct the agent to post the verdict to Jira and update the ticket accordingly.

Frequently Asked Questions about jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I post code review verdicts to Jira issues automatically?

You can post code review verdicts to Jira by instructing the agent after a review completes, provided Jira context such as a project key, issue number, or Atlassian MCP connection is available. It posts a concise comment to the relevant Jira issue.

Can I flag blockers on a Jira ticket after a code review?

Yes, flagging blockers on a Jira ticket after a code review is supported. The Skill explicitly flags blockers in the Jira issue comment and suggests appropriate workflow transitions like Ready for QA or Needs Rework.

Does this Jira integration work without an Atlassian MCP connection?

An Atlassian MCP connection is one way to provide Jira context, but you can also use a project key or issue number. The Skill works as long as some Jira context is available to identify the target issue.

How do I update Jira workflow transitions based on code review outcomes?

To update Jira workflow transitions based on review outcomes, finish a code review and instruct the agent to post the verdict. The Skill suggests the next workflow transition, such as Ready for QA or Needs Rework, based on the review result.

What Jira context is needed to sync code review outcomes with tickets?

To sync code review outcomes with Jira tickets, you need Jira context such as a project key, issue number, or an active Atlassian MCP connection. Without this context, the Skill cannot determine which Jira issue to update.

When should I not use automated Jira comments for code review verdicts?

You should not use automated Jira comments for code review verdicts when no Jira context is available, or when a review is still in progress, since the Skill applies only after a review is complete and the target issue is identifiable.