workflow

Automates Git feature branches from Jira tickets through commit-to-PR lifecycle with quality checks.

2|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill workflow-eso-toolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/ESO-Toolkit/eso-toolkit/tree/main/.github/skills/workflow
Command: npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill workflow-eso-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures adherence to the ESO Log Aggregator's Git workflow, preventing commits to protected branches and automating the creation and management of feature branches tied to Jira tickets.

Core Features & Use Cases

  • Branch Protection: Prevents direct commits to main or master branches.
  • Automated Branching: Creates correctly named feature branches (ESO-XXX/description) either in a new worktree or in-place, based on Jira ticket references.
  • Workflow Enforcement: Guides the user through quality checks, commits, pushes, and Pull Request creation.
  • Jira Integration: Automatically updates Jira ticket status as work progresses.
  • Use Case: When you mention a Jira ticket like ESO-123, this skill automatically creates a new branch named ESO-123/your-description, ensuring your work is properly tracked and preventing accidental commits to main.

Quick Start

Start working on ticket ESO-670 by creating a new feature branch.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I automate git workflow and prevent direct commits to main?

Automating git workflow prevents direct commits to main by enforcing branch protection and guiding you through quality checks before pull request creation. It ensures adherence to the ESO Log Aggregator Git workflow.

Can I automatically create feature branches from Jira ticket references?

Yes, you can create feature branches from Jira ticket references. Mentioning a ticket like ESO-123 automatically creates a new branch named ESO-123/your-description, either in-place or in a separate worktree.

How does the pull request lifecycle work with automated branching?

The pull request lifecycle validates branch state and handles uncommitted changes before pushing. It automates pull request creation while running quality gate checks to ensure code readiness.

Does this git workflow automation handle uncommitted changes before branching?

Yes, this git workflow automation handles uncommitted changes before creating branches. It validates the current branch state and manages pending modifications to ensure a clean working tree.

What is the best way to track parent dependencies when creating feature branches?

The best way to track parent dependencies is by registering them using twig or git config. This maintains the hierarchical relationship between branches during automated creation.