dev-build

Automate Linear-issue coding workflows through build, review, gate, and ship steps.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/tezra-io/agentic-coding-workflow-skills --skill dev-build-tezra-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-build
Source: https://github.com/tezra-io/agentic-coding-workflow-skills/tree/main/skills/dev-build
Command: npx skills add https://github.com/tezra-io/agentic-coding-workflow-skills --skill dev-build-tezra-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone coordination of end-to-end coding workflows for Linear-tracked tasks, removing the need to manually manage build, review, gate, and ship steps for each individual issue.

Core Features & Use Cases

  • Linear Issue Iteration: Automatically processes prioritized Linear issues for a target project, skipping stale, completed, or blocked tasks, and auto-closing issues already shipped in git history.
  • TDD Build & Gate Coordination: Spawns Codex for test-driven implementation, runs full project validation gates (linting, tests, formatting), and tracks baseline debt from pre-existing test failures.
  • Mandatory Review & Safe Shipping: Enforces separate Claude code review to catch integration issues and regressions, routes fix loops only when review fails, and ships passing changes to the default branch with standardized commit formatting. Use case: An engineering team can use this Skill to automatically process a backlog of 15 prioritized Linear bugs and features, running each through implementation, review, and ship without manual orchestration, while safely skipping any issues already completed in prior commits.

Quick Start

Invoke the dev-build skill with your target project name to automatically process all actionable Linear issues for that project through implementation, review, and shipping.

Frequently Asked Questions about dev-build

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

FAQPage Schema
How do I automate the coding workflow from Linear issue tracking through to git shipping?

Automating the coding workflow from Linear issue tracking to git shipping requires coordinating build, review, gate, and ship steps. This Skill automatically processes actionable Linear issues through test-driven implementation, mandatory code review, and branch shipping without manual orchestration, skipping stale or blocked tasks.

Does the automated code review process use Claude CLI separate from the implementation step?

Yes, the automated code review process uses Claude CLI separately from the implementation step. This Skill spawns Codex CLI for test-driven implementation and enforces a separate Claude code review to catch integration issues and regressions, routing fix loops only when the review fails.

Can I use Codex CLI for test-driven development while enforcing full project gate validation?

Yes, you can use Codex CLI for test-driven development while enforcing full project gate validation. This Skill spawns Codex for implementation and automatically runs linting, tests, and formatting gates, while tracking baseline debt from pre-existing test failures to ensure safe shipping.

What is the best way to handle a backlog of Linear bugs and features through implementation and review?

The best way to handle a backlog of Linear bugs and features is invoking this Skill with a target project name. It automatically processes all actionable issues through implementation, review, and shipping, while safely skipping any issues already completed in prior commits to avoid duplicate work.

How does automated branch shipping handle commit formatting and repository state validation?

Automated branch shipping handles commit formatting and repository state validation by enforcing standardized commit formatting and git-based state checks. This Skill ships passing changes to the default branch only after full gate validation and code review pass, ensuring safe, conflict-free shipping.

Do I need Linear, Codex CLI, and Claude CLI integrations to run the end-to-end coding workflow?

Yes, you need Linear, Codex CLI, and Claude CLI integrations to run the end-to-end coding workflow. This Skill requires Linear for issue tracking, Codex CLI for implementation tasks, Claude CLI for code review, and git-based repository state validation to ensure safe, conflict-free shipping.