skills.rest
maisonnat
maisonnatCOMMUNITY
Explore all skills by this author →
GitHub

ops_local_dev

Coordinate local development and staged production promotion with START, WORK, VERIFY, and PROMOTE phases.

Updated Aug 23, 2026
Search Tags:#devops#workflow automation#local development#promotion#pre-flight checks#release gating#git commit workflow
One-click install
npx skills add https://github.com/maisonnat/axur-tool --skill ops-local-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops_local_dev
Source: https://github.com/maisonnat/axur-tool/tree/main/.agent/skills/ops_local_dev
Command: npx skills add https://github.com/maisonnat/axur-tool --skill ops-local-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local development workflows with controlled promotion to production.

Core Features & Use Cases

  • Guided START/WORK/VERIFY/PROMOTE phases for local development and safe production handoff.
  • Clear start-up instructions to boot backend and frontend locally and verify endpoints.
  • Dry-run/promote gates that require explicit confirmation before pushing changes to production.

Quick Start

Run the local development script to start the backend and frontend locally and enter the gated promotion workflow.

Frequently Asked Questions about ops_local_dev

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

FAQPage Schema
How do I set up a local development workflow with gated production promotion?▼

Local development workflows with controlled promotion use guided START, WORK, VERIFY, and PROMOTE phases to coordinate feature development and safely hand off changes. Start scripts boot backend and frontend locally before entering the gated promotion process.

What are pre-flight checks in a git commit workflow for release gating?▼

Pre-flight checks are validation steps applied during the VERIFY phase of a local development workflow. They act as release gates, ensuring feature stability and endpoint verification before any dry-run promotion or production deployment occurs.

Can I require explicit confirmation before pushing local development changes to production?▼

Yes, dry-run promotion and production deployment gates require explicit confirmation before pushing changes. This controlled promotion mechanism prevents accidental production releases during local development handoffs.

Does this local development workflow support separate validation phases for feature deployment?▼

The workflow specifies four distinct phases: START, WORK, VERIFY, and PROMOTE. Software teams use these separate stages to perform feature development, validation, and staged deployment with controlled production handoffs.

What is the best way to boot backend and frontend locally before a production handoff?▼

Run the local development start scripts to boot the backend and frontend locally. These startup instructions verify endpoints and prepare the environment for the subsequent gated promotion workflow.

Why use dry-run promotion gates in a local dev and release workflow?▼

Dry-run promotion gates test the deployment process without affecting production. They provide an explicit confirmation checkpoint during the PROMOTE phase, ensuring safe production handoff from local development.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
tachyon-beeptachyon-beep
14

cicd-pipeline-architecture

Architect CI/CD pipelines with deployment strategies, test gates, and rollback mechanisms.

Community
Advanced
TechsioCZTechsioCZ
2

ui-kit-publish-readiness

Validate UI kit exports, tokens, Storybook, and semantic-release constraints.

Official
Intermediate
santosomarsantosomar
1

cd-pipeline-generator

Generate CD pipelines with environment promotion, approval gates, and rollback triggers.

Community
Advanced