chief-push

Automate a multi-phase pre-push quality gate with debug, lint, test, and branch checks.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/onlypfachi/chief --skill chief-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chief-push
Source: https://github.com/onlypfachi/chief/tree/main/chief-push
Command: npx skills add https://github.com/onlypfachi/chief --skill chief-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures code changes do not leave the developer workstation without passing a comprehensive, multi-phase quality gate, reducing risky pushes and production incidents.

Core Features & Use Cases

  • Phase-based gates: debug scan, lint, tests, branch checks, version bump, commit, and push to enforce discipline.
  • Guided collaboration: prompts, branch-name suggestions, and approval steps to align with team workflows.
  • Safety-first push: deterministic checks and actionable feedback to keep regressions out of main branches.

Quick Start

Run chief-push to execute the full pre-push quality gate, including debug scan, lint, tests, and branch checks.

Frequently Asked Questions about chief-push

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

FAQPage Schema
How do I enforce code quality checks before pushing to a shared git branch?

You can enforce code quality before a git push by running a multi-phase pre-push quality gate that scans for debug statements, runs lint, executes tests, and validates branch setup. This prevents buggy code from reaching shared branches.

What is a pre-push quality gate and how does it prevent risky pushes?

A pre-push quality gate is a deterministic set of checks—debug scans, lint, tests, and branch validation—that code must pass before leaving your workstation. It enforces discipline and keeps regressions out of shared branches.

How do I automate debug scans, lint, and tests before committing changes?

You can automate these checks by running a structured pre-push flow that sequentially gates debug scans, lint, tests, and version bumps before allowing a commit. This provides actionable feedback to fix issues before pushing.

Can I get automatic branch-name suggestions and approval prompts during git push?

Yes, a guided pre-push quality gate can prompt for approvals and suggest branch names to align with team workflows. This ensures structured collaboration and enforces safety-first pushes to shared branches.

Does this pre-push gate work for individual developers or does it require a team setup?

This pre-push gate works for both individual developers and teams who push code. It applies deterministic checks and provides actionable feedback on the workstation, requiring no specific team infrastructure to enforce discipline.

What steps are included in a structured pre-push workflow to keep regressions out of main?

A structured pre-push workflow includes phase-based gates for debug scans, lint, tests, branch checks, version bumps, and a final push guardrail. These steps collectively prevent risky pushes and production incidents.