workflow

Manage Jira issue transitions, branch creation, and pull requests.

1|Updated Oct 3, 2023
One-click install
npx skills add https://github.com/mt-krainski/twinkletaps --skill workflow-mt-krainski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/mt-krainski/twinkletaps/tree/main/.claude/skills/workflow
Command: npx skills add https://github.com/mt-krainski/twinkletaps --skill workflow-mt-krainski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized, efficient process for managing software development tasks, from planning and implementation to review and merging, ensuring consistency and clarity in the development lifecycle.

Core Features & Use Cases

  • Jira Task Management: Transition issues, create branches, and manage task statuses within Jira.
  • Development Workflow Enforcement: Adheres to principles of small, reviewable increments and a defined lifecycle (Plan → Build → Review → Merge).
  • Naming Conventions: Enforces consistent naming for branches, commits, and PRs.
  • Use Case: When you need to move a Jira task from 'To Do' to 'In Progress', create a new feature branch, and then later transition it to 'Review' after code is ready.

Quick Start

Use the workflow skill to transition Jira issue GFD-123 to 'In Progress'.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I automate Jira task transitions when moving issues through the development workflow?

Automate Jira task transitions by integrating with Jira for task tracking to move issues from 'To Do' to 'In Progress' and 'Review' based on your defined software development lifecycle stages. This enforces incremental development principles.

What's the best way to enforce consistent branch naming conventions during agile development?

Enforce consistent branch naming conventions by utilizing a workflow automation process that manages branch creation according to predefined rules. This ensures consistency across branches, commits, and pull requests linked to Jira issues.

How does code review integration work with task management in Jira?

Code review integration works by transitioning Jira issues to a 'Review' state when code is ready, facilitating pull request management. This enforces the lifecycle stage of reviewing small, reviewable increments before merging.

Does this workflow automation approach support incremental development processes?

Yes, this workflow automation supports incremental development by enforcing a defined lifecycle of Plan, Build, Review, and Merge. It manages software development tasks to ensure adherence to principles of small, reviewable code increments.

Can I manage pull request creation and task statuses directly within Jira?

Yes, you can manage pull request creation and task statuses directly within Jira. The workflow facilitates issue transitions, branch creation, and pull request management according to defined naming conventions and process stages.