jira

    1

    Automate Jira ticket creation, daily progress logging from git history, and sprint management via MCP.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    jira

    Example session with this skill installed

    I'm wrapping up for the day. Check my work and log it on the right Jiras. I also need to create a new story for the API rate limiting feature under the Platform epic.

    • Read your context and instructions
    • Compiled the jira

    I have analyzed your activity from today. You made three commits in the auth-service repo and completed the JWT validation logic. I also found a relevant ticket in your current sprint.

    For the new story, I have retrieved the metadata for project ABC.

    Proposed Jira Actions

    New Story: API Rate Limiting

    FieldValue
    SummaryImplement API rate limiting for guest endpoints
    EpicABC-123 (Platform)
    StageBacklog
    Points3
    DescriptionPrevent service exhaustion by limiting unauthenticated requests to 100 per minute.
    Acceptance Criteria1. Middleware returns 429 status when limit exceeded. 2. Rate limits are configurable via env vars. 3. Headers include X-RateLimit-Remaining.

    EOD Update: ABC-455 (Fix JWT Refresh)

    Done today:

    • Implemented RSA256 signature verification in verify.go.
    • Added unit tests for expired token handling.
    • Verified fix with curl -I -H "Authorization: Bearer <token>" returning 200.

    Next:

    • Integration testing with the frontend client.

    Next steps

    1. Would you like me to create the new story and post the comment to ABC-455?
    2. Shall I assign the new story to you?
    3. Should I log the 2 hours spent on ABC-455?

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Jira management is often a manual chore that lags behind actual development work. This skill automates the overhead of ticket creation and daily reporting by bridging the gap between your terminal, your git logs, and Jira Cloud. It handles the tedious parts of Jira—like fetching custom field IDs, mapping open sprints, and drafting acceptance criteria—so you can focus on writing code.

    What it does

    • Standardized ticket creation generates stories with required custom fields, epics, and acceptance criteria.
    • Automated EOD reporting scans local session logs and git commits to draft progress comments on active tickets.
    • Workflow transitions fetches valid transitions for any ticket and moves them through your project pipeline.
    • Smart search executes JQL queries to find tickets by assignee, sprint, or status category.
    • Work logging posts technical notes, command outputs, and time tracking directly to issues.

    How it works

    1. Metadata retrieval fetches current project schemas to identify required custom fields and allowed dropdown values.
    2. Context gathering queries the Atlassian MCP server to sync with your site URL and active board IDs.
    3. Drafting and approval presents ticket details or EOD updates in a compact table for your confirmation before posting.
    4. Execution calls MCP tools like createJiraIssue or addWorklogToJiraIssue to update the Jira site.

    Frameworks & tools

    This skill requires the Atlassian MCP server. It utilizes Jira Cloud REST APIs via MCP tools and interacts with local dev environments using git and filesystem commands.

    Why this beats prompting it yourself

    Generic prompts fail to handle Jira's complex custom field IDs and specific sprint metadata requirements. This skill enforces project conventions, like mandatory epic links and testable acceptance criteria, while sourcing real data from your git history to ensure updates are accurate and not hallucinated.

    Use cases

    • Generating a batch of development stories from a project requirements list.
    • Drafting and posting "end of day" progress updates based on today's commits.
    • Logging terminal output and test results as comments on a specific bug ticket.
    • Moving an assigned ticket to 'Done' while simultaneously logging time spent.

    Known limitations

    Requires the Atlassian MCP server to be installed and authenticated. Only supports 'Story' issue types for new ticket creation and requires a pre-configured Scrum board ID.

    Requires Atlassian MCP server. Ticket creation is limited to Story types. User must provide site URL, project key, and board ID. EOD reports depend on local Claude session logs and git history.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    • Free with an Agensi account

    Requires

    Git

    Permissions

    Terminal / Shell
    Write Files
    Network Access
    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This skill eliminates the need to manually look up project-specific metadata by automatically fetching your Jira site's custom field IDs, active sprint boards, and valid workflow transitions.

    Yes, this skill requires the Atlassian MCP server to be installed and authenticated to your Jira Cloud account, along with access to your local git environment.

    The skill scans your local git commits and session logs to generate accurate, technical summaries of your work, which you can review before they are posted as comments or worklogs.

    Currently, the ticket creation feature is optimized for 'Story' issue types, though it can transition and comment on any existing issue type within your project.

    This skill is designed for any AI agent that supports the Model Context Protocol (MCP), specifically those capable of interacting with the Atlassian MCP server.

    New in Agents & Orchestration