Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Ticket to Branch: Git Diff to Jira Ticket, Branch & Push

    2

    Automates the entire flow from local git diff to tracker ticket, branch creation, and remote push.

    $6

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    12 uses5.0 (2 reviews)
    Ticket to Branch: Git Diff to Jira Ticket, Branch & Push

    Ticket to Branch: Git Diff to Jira Ticket, Branch & Push

    Example session with this skill installed

    ship this to Linear, it is a task for the platform team that fixes the refund rejection state.

    • Read your context and instructions
    • Compiled the ticket to branch

    Ticket created: [PLAT-129] Show 'Not refunded' state for rejected returns.
    Assigned to active cycle: Cycle 42.
    Branch created and pushed: plat-129/refund-rejection-fix.
    Status: Moved to 'In Review'.
    PR Link: https://github.com/org/repo/pull/new/plat-129/refund-rejection-fix

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

    About this skill

    The problem

    Developers spend too much time on manual bookkeeping after finishing a feature. Manually creating Jira/Linear tickets, mapping them to sprints, naming branches to match keys, and pushing PRs creates context-switching friction and leads to inconsistent repo history.

    What it does

    • Analyzes your current git diff to generate professional ticket summaries and descriptions.
    • Identifies the correct project and active sprint to ensure work appears on the right board.
    • Creates a policy-compliant git branch and commits work using conventional commit standards.
    • Pushes to remote and transitions the tracker ticket to a review state only after a successful push.
    • Reports the final ticket URL, branch name, and PR creation link in a single summary.

    Frameworks & tools

    Works with Jira, Linear, GitHub Issues, and Azure Boards. Uses standard Git CLI, gh CLI, and az boards.

    Why this beats prompting it yourself

    A simple prompt might hallucinate ticket IDs or fail to handle the specific GraphQL or API requirements of your tracker. This skill implements a strict state machine that prevents duplicate tickets, respects local git hooks, and ensures the branch name, commit message, and ticket key stay perfectly synced.

    Use cases

    • Convert a messy working directory into a tracked Jira ticket and pushed branch.
    • File a bug fix discovered during development without leaving the terminal.
    • Ensure every commit in a repository follows strict ticket-key prefixing rules.
    • Batch move local experimental work into the team's active sprint/cycle.

    Known limitations

    Requires authenticated CLI tools for your specific tracker. Cannot resolve which project or sprint to use if the workspace is ambiguous, so it will stop and ask for clarification.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires pre-authenticated CLI access (gh, az, or Jira/Linear credentials). Will not guess project or sprint destinations; user must provide them if ambiguous.

    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 buying a skill.

    Reviews

    5.0
    2 reviews
    5
    2
    4
    0
    3
    0
    2
    0
    1
    0

    This skill has been used 12 times.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Terminal / Shell
    Listed2 months ago
    Updatedtoday

    What's inside

    Frequently Asked Questions

    This skill is designed for AI agents that have terminal or local environment access, such as Open Interpreter, AutoGPT, or custom LangChain-based development assistants. It bridges the gap between your local Git environment and your project management API.

    No, you don't need to provide credentials to the agent. The skill utilizes your existing local CLI authentications (like `gh auth` or `jira-cli`), ensuring your API keys and tokens remain securely stored on your machine.

    The skill includes a 'sanity check' phase where it validates that your current Git diff aligns with the generated ticket. If there is an ambiguity regarding which project or sprint the work belongs to, the skill is programmed to pause and ask for your input rather than guessing.

    Yes, the skill is configured to follow Conventional Commits and standard branch naming conventions (e.g., `feature/PROJECT-123-description`). It ensures that the ticket key is perfectly synced across your tracker, branch name, and commit history.

    You receive the complete skill definition, including the state machine logic for handling tracker APIs and Git operations. Additionally, you get a setup guide to ensure your local environment is correctly configured to support the automation.

    New in Agents & Orchestration