jira-geo

Automate GEO Jira issue transitions across the standard board workflow.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill jira-geo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-geo
Source: https://github.com/tecnologia-ibtech/geo-codex/tree/main/geo-ops/skills/jira-geo
Command: npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill jira-geo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moves GEO Jira tasks through the GEO workflow, ensuring consistent status updates and correct field handling across transitions.

Core Features & Use Cases

  • Transition GEO issues along the board (To Do → In Development → Ready to Review → In Review → Done) and manage the Paused state.
  • Automatically populate and validate required fields during transitions (e.g., resolution, custom fields like Procedure Description or Pull requests).
  • Support the /jira-geo command to update or advance tasks (e.g., GEO-XXXX) and synchronize with Jira transitions.

Quick Start

Run /jira-geo with the GEO issue key to move the task to its next appropriate state.

Frequently Asked Questions about jira-geo

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

FAQPage Schema
How do I automate Jira task transitions through the GEO workflow board?

Automate Jira task transitions through the GEO workflow board by running the /jira-geo command with the GEO issue key to move tasks from To Do to Done. The Skill automatically fetches available transitions and applies the correct status updates along the standard board path.

What happens to mandatory Jira fields when moving a GEO issue to In Review?

Mandatory Jira fields, such as resolution, Procedure Description, or Pull requests, are automatically populated and validated when moving a GEO issue to In Review. This ensures correct field handling across transitions and prevents incomplete status updates.

Can I move a GEO Jira issue into a Paused state using task automation?

Yes, you can move a GEO Jira issue into a Paused state using task automation. The workflow supports the Paused path alongside the standard board transitions, allowing you to suspend task progression and resume it later when ready.

Do I need to manually fetch available transitions before updating a GEO Jira issue?

No, you do not need to manually fetch available transitions before updating a GEO Jira issue. The automation uses getTransitionsForJiraIssue internally to retrieve valid transitions and populate mandatory fields during the status update process.

Why does my GEO Jira task transition fail when moving to In Development?

GEO Jira task transitions fail when mandatory custom fields, like Procedure Description or Pull requests, are missing or invalid. The workflow requires fetching available transitions and ensuring all required fields are correctly populated before applying the status change.