git-ops

Standardize Git commits, branching, pre-merge checks, and deployments for CYPHER V3.

4|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill git-ops-0xjc65eth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-ops
Source: https://github.com/0xjc65eth/CYPHER-V3/tree/main/skills/git-ops
Command: npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill git-ops-0xjc65eth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, consistent Git workflow and deployment checklist for the CYPHER V3 repository to reduce noisy commits, avoid merge conflicts, prevent broken builds in production, and ensure secrets are never committed.

Core Features & Use Cases

  • Conventional Commits: Enforces structured commit messages (feat|fix|perf|security|etc.) scoped to repository modules for discoverability and changelog automation.
  • Branching Strategy: Defines protected main and staging branches, feature/fix/hotfix branch patterns, and a PR-driven merge flow.
  • Pre-commit & CI Checks: Recommends Husky hooks that run type checking and linting to block commits that would break builds or quality gates.
  • Deploy Pipeline & Recovery: Details automatic Vercel production deploys from main, PR previews, optional Railway workflow, and Docker run instructions for local/staging testing.
  • Checklist & Hygiene: Includes a pre-merge checklist to verify builds, audits, no hardcoded secrets, and conventional commit compliance.

Quick Start

Create a feature branch, run the pre-commit checks (type-check and lint), commit with a conventional message, push the branch, and open a pull request for review.

Frequently Asked Questions about git-ops

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

FAQPage Schema
How do I enforce conventional commits with Husky pre-commit hooks?

Husky pre-commit hooks enforce conventional commits by automatically running type checking and linting before a commit is finalized, blocking code that breaks quality gates or violates structured message formats.

What is the best way to structure Git branching for staging and production deployments?

The best way to structure Git branching for deployments uses protected main and staging branches alongside dedicated feature, fix, and hotfix branch patterns with a pull request-driven merge flow.

How do I prevent hardcoded secrets from being committed in a CI-CD pipeline?

To prevent hardcoded secrets in a CI-CD pipeline, apply a pre-merge checklist that verifies secret hygiene, successful builds, and audit compliance before any code merges into protected branches.

How do I configure Vercel and Railway deployments for a Dockerized repository?

Configure deployments by setting up automatic Vercel production deploys from the main branch, using PR previews, and utilizing Docker run instructions for local or staging testing with an optional Railway workflow.

Why do my Git commits fail type checking and linting checks before merging?

Git commits fail type checking and linting because pre-commit Husky hooks execute these checks to block commits that would break builds, ensuring only verified code enters protected staging branches.

Do I need a pull request to merge a hotfix into the main branch?

Yes, you need a pull request to merge a hotfix into the main branch because the main branch is protected and requires a PR-driven merge flow to pass pre-merge checks and maintain deployment stability.