update-hooks

Updates git hooks in an existing project to the latest Bravros template version.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill update-hooks-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-hooks
Source: https://github.com/bravros/bravros/tree/main/plugins/tools/skills/update-hooks
Command: npx skills add https://github.com/bravros/bravros --skill update-hooks-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Git hooks installed in a project become outdated when the Bravros templates change, leaving commit validation and push protection rules stale. This Skill refreshes the hooks in an existing repository to the latest version without touching workflows or planning files. ## Core Features & Use Cases - Hook Refresh: Overwrites .bravros/hooks/commit-msg and .bravros/hooks/pre-push with the latest template versions via bravros init --skip-workflows --skip-staging-branch. - Prerequisite Checks: Verifies the current directory is a git repository and that .bravros/hooks/ exists before updating, suggesting /start if hooks were never installed. - Scoped Update: Intentionally leaves .github/workflows and .planning untouched and never commits automatically, so the user can review changes. - Use Case: After upgrading the Bravros CLI, run this Skill in each existing project so commit message validation and the direct-push-to-main guard match the newest rules. ## Quick Start Update the git hooks in this repository to the latest Bravros template version.

Frequently Asked Questions about update-hooks

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

FAQPage Schema
How do I update git hooks in an existing project?▼

Run the update-hooks skill inside the repository, which executes bravros init --skip-workflows --skip-staging-branch. This overwrites .bravros/hooks/commit-msg and .bravros/hooks/pre-push with the latest template versions.

How do I refresh Bravros hooks after upgrading the CLI?▼

Invoke the update-hooks skill in each existing project after upgrading Bravros. It rewrites the hook files from the newest templates while leaving workflows and planning files untouched.

What happens if .bravros/hooks does not exist in my repository?▼

The skill checks for .bravros/hooks before updating and suggests running /start if the directory is missing. Hooks must be installed first before they can be refreshed.

Does updating git hooks modify my GitHub workflows or commit changes?▼

No. The update intentionally skips .github/workflows and .planning, and it never commits automatically. You review the changed hook files and commit them yourself.

Which git hooks get updated by this process?▼

Two hooks are refreshed: commit-msg, which enforces the latest commit validation rules, and pre-push, which prevents direct pushes to main. Both live under .bravros/hooks via core.hooksPath.