How do I install the Precommit Workflow Management skill?

Run npx skillmds@latest add mishrashardendu22/precommit-workflow-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Precommit Workflow Management safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Precommit Workflow Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Precommit Workflow Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Precommit Workflow Management?

MishraShardendu22 (@mishrashardendu22) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Precommit Workflow Management by mishrashardendu22

Name: Precommit Workflow Management
Author: MishraShardendu22

File contents

Pre-Commit Workflow Management Skill

This skill explains how to maintain, configure, and execute the intelligent pre-commit hook workflow in the GitHub Backup Automation System monorepo.

1. Branch-First Development

[!IMPORTANT] CREATE A LOCAL BRANCH FIRST: Always start by creating a local branch from main:
git switch -c MishraShardendu22/main/<feature-name>
Never make changes directly on main.

2. Pre-Commit Architecture

The pre-commit workflow lives in .githooks/pre-commit and is tracked directly in version control.

Staged Changes Detected (git diff --cached)
  │
  ├── Only Go files changed ───────► Run Go formatting, vet, tests, build (~1-2s)
  ├── Only Python files changed ───► Run Pyright typecheck, agent test suite (~3-4s)
  ├── Only Frontend files changed ─► Run Biome lint, Next.js build (~10-12s)
  ├── Only Documentation changed ──► Fast-path bypass (<0.2s)
  └── Global / Config / Manual ────► Full monorepo validation gate (~20s)

2. Key Features

Selective Staged-File Execution: Avoids unnecessary work by only running checks relevant to the files staged for the commit.
Fast-Path for Documentation: Commits containing only markdown (*.md), text (*.txt), or asset files skip expensive build and test pipelines.
Subshell Directory Isolation: Every check runs in a subshell (cd "${REPO_ROOT}" && ...) to prevent current working directory drift.
Fail-Fast with Remediation: Aborts immediately on failure and outputs exact commands needed to fix the problem.
Zero External Runtime Dependencies: Implemented in portable POSIX bash, requiring no npm wrapper packages (like Husky) at the repository root.

3. Operations & Maintenance Runbook

Activating the Hook Locally

make hooks-install
# Or: ./scripts/install-hooks.sh

Manually Running Pre-Commit Gate

make pre-commit

Bypass Flags (Emergency Only)

# Skip tests for quick drafts
SKIP_TESTS=1 git commit -s -S -m "chore: draft"

# Skip builds for lightweight edits
SKIP_BUILDS=1 git commit -s -S -m "fix: comment"

# Force full validation across all subsystems
PRECOMMIT_ALL=1 git commit -s -S -m "feat: core change"

---name: precommit-workflow-managementdescription: Rules, architecture, and runbooks for configuring, updating, and operating the intelligent Git pre-commit workflow.---# Pre-Commit Workflow Management SkillThis skill explains how to maintain, configure, and execute the intelligent pre-commit hook workflow in the **GitHub Backup Automation System** monorepo.## 1. Branch-First Development> [!IMPORTANT]> **CREATE A LOCAL BRANCH FIRST**: Always start by creating a local branch from `main`:> ```bash> git switch -c MishraShardendu22/main/<feature-name>> ```> Never make changes directly on `main`.---## 2. Pre-Commit ArchitectureThe pre-commit workflow lives in `.githooks/pre-commit` and is tracked directly in version control.```textStaged Changes Detected (git diff --cached) │ ├── Only Go files changed ───────► Run Go formatting, vet, tests, build (~1-2s) ├── Only Python files changed ───► Run Pyright typecheck, agent test suite (~3-4s) ├── Only Frontend files changed ─► Run Biome lint, Next.js build (~10-12s) ├── Only Documentation changed ──► Fast-path bypass (<0.2s) └── Global / Config / Manual ────► Full monorepo validation gate (~20s)```---## 2. Key Features1. **Selective Staged-File Execution**: Avoids unnecessary work by only running checks relevant to the files staged for the commit.2. **Fast-Path for Documentation**: Commits containing only markdown (`*.md`), text (`*.txt`), or asset files skip expensive build and test pipelines.3. **Subshell Directory Isolation**: Every check runs in a subshell `(cd "${REPO_ROOT}" && ...)` to prevent current working directory drift.4. **Fail-Fast with Remediation**: Aborts immediately on failure and outputs exact commands needed to fix the problem.5. **Zero External Runtime Dependencies**: Implemented in portable POSIX bash, requiring no npm wrapper packages (like Husky) at the repository root.---## 3. Operations & Maintenance Runbook### Activating the Hook Locally```bashmake hooks-install# Or: ./scripts/install-hooks.sh```### Manually Running Pre-Commit Gate```bashmake pre-commit```### Bypass Flags (Emergency Only)```bash# Skip tests for quick draftsSKIP_TESTS=1 git commit -s -S -m "chore: draft"# Skip builds for lightweight editsSKIP_BUILDS=1 git commit -s -S -m "fix: comment"# Force full validation across all subsystemsPRECOMMIT_ALL=1 git commit -s -S -m "feat: core change"```

Frequently asked questions

Precommit Workflow Management