skills.rest
namuan
namuanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ticket-mode

Automates Jira ticket-to-GitHub-PR workflows including polling, branching, and PR generation.

4|Updated Dec 11, 2022
Search Tags:#automation#workflow#integration#github#jira#pull-request#ticketing
One-click install
npx skills add https://github.com/namuan/namuan --skill ticket-mode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-mode
Source: https://github.com/namuan/namuan/tree/main/agents/skills/ticket-mode
Command: npx skills add https://github.com/namuan/namuan --skill ticket-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ticket mode automates the end-to-end handling of development tickets by continuously polling Jira for ready issues, translating them into actionable tasks, and creating GitHub pull requests to merge the work.

Core Features & Use Cases

  • Continuous issue intake: poll Jira for ready issues and filter them to ensure meaningful work.
  • Automation of workflow: transition issues to In Progress, sync with main, create and manage feature branches, and generate PRs.
  • Use Case: For a team that tracks work in Jira and ships via GitHub, this skill bridges the gap by automatically turning ready tickets into PRs, reducing manual handoffs.

Quick Start

Run ticket mode to automatically convert ready Jira issues into GitHub pull requests.

Frequently Asked Questions about ticket-mode

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

FAQPage Schema
How do I automate Jira to GitHub pull request workflows?▼

Automating Jira to GitHub pull request workflows involves continuously polling Jira for ready issues, transitioning them to In Progress, creating feature branches, and automatically generating GitHub pull requests to merge the work.

What is the best way to convert ready Jira issues into GitHub branches automatically?▼

The best way to convert ready Jira issues into GitHub branches automatically is to use an orchestration workflow that polls Jira, filters meaningful work, syncs with main, and handles feature branch creation before generating a pull request.

Can I automatically transition Jira ticket status when creating a pull request?▼

Yes, you can automatically transition Jira ticket status when creating a pull request by using a workflow that moves issues to In Progress, syncs with the main branch, and generates a pull request to bridge the gap.

Does automated Jira to GitHub ticket workflow include guardrails against unsafe changes?▼

Automated Jira to GitHub ticket workflows include guardrails designed to prevent unsafe changes, ensuring that only filtered and meaningful issues are translated into actionable tasks and pull requests.

How does continuous issue intake from Jira for pull request generation work?▼

Continuous issue intake from Jira for pull request generation works by continuously polling Jira for ready issues, applying filters to ensure meaningful work, and translating those issues into actionable GitHub pull requests.

Related Skills

Explore More Software Engineering Skills→
al-steval-stev

atlassian-setup

Configure Atlassian API credentials for Jira and Confluence access.

Community
Intermediate
pekralpekral

resolve-jira-issue

Resolve JIRA issues by implementing fixes and creating GitHub pull requests.

Community
Advanced
tylerbutlertylerbutler

trigger-pipelines-for-copilot-pr

Trigger Azure DevOps pipelines for Copilot pull requests via GitHub comments.

Community
Intermediate
blocknaviblocknavi
1

convex-http-actions

Expose HTTP endpoints for Convex webhooks and external API calls.

Official
Advanced