Verified:GitHub

devflow:build-ops

Dispatch issue and VCS operations to Jira, GitLab, and GitHub backends.

Updated Aug 23, 2026

Search Tags:#automation #github #jira #gitlab #devflow #issue-tracking

One-click install

npx skills add https://github.com/codingthefuturewithai/claude-code-primitives --skill devflow-build-ops

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: devflow:build-ops
Source: https://github.com/codingthefuturewithai/claude-code-primitives/tree/main/skills/build-ops
Command: npx skills add https://github.com/codingthefuturewithai/claude-code-primitives --skill devflow-build-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines cross-backend DevFlow workflows by coordinating issue tracking and VCS operations through a single dispatcher and policy-driven MCP calls.

Core Features & Use Cases

Config loading for backend choices and mandatory parameters
Mandatory parameter validation gate before any MCP calls
End-to-end operation routing for Jira, GitLab, GitHub and related VCS tasks

Quick Start

Configure backends with /devflow-setup and then run /devflow:build:workflow-guide to view the end-to-end process

Frequently Asked Questions about devflow:build-ops

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

FAQPage Schema

How do I automate issue tracking and VCS operations across Jira, GitLab, and GitHub?▼

Cross-backend DevOps workflows are coordinated through a single dispatcher that routes end-to-end build operations to Jira, GitLab, and GitHub. It uses policy-driven MCP calls to implement, validate, and close issues, MRs, and PRs across diverse backends.

What is the best way to ensure safe, auditable automation for GitLab and GitHub workflows?▼

Auditable automation is ensured by enforcing strict backend isolation, explicit provenance, and mandatory parameter validation before executing MCP tool calls. This approach provides robust error handling for safe VCS operations across Jira, GitLab, and GitHub.

How do I set up backend configurations for issue tracking and VCS automation?▼

Backend configurations for issue tracking and VCS automation are set up by loading backend choices and mandatory parameters during initialization. Once configured, the dispatcher validates these inputs before routing any MCP tool calls to the selected platforms.

Does this dispatcher support isolated operations for Jira issue tracking?▼

Yes, the dispatcher supports isolated operations for Jira issue tracking by enforcing strict backend isolation. This ensures MCP calls and parameter validation specific to Jira remain separate from GitLab and GitHub VCS workflows.

Why does parameter validation matter before dispatching MCP tool calls?▼

Parameter validation matters because it acts as a mandatory gate before dispatching MCP tool calls to Jira, GitLab, or GitHub. This prevents invalid inputs from executing VCS operations, ensuring robust error handling and safe build workflow automation.