workflow-sync

Update an existing project's git hooks, GitHub Action, and DB sync template to the latest workflow setup.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Projects set up with an older Bravros workflow drift out of date as hooks, CI workflows, and templates improve, and manually tracking which files to overwrite versus preserve is error-prone. ## Core Features & Use Cases - Selective File Updates: Overwrites git hooks (commit-msg, pre-push) and the GitHub Action workflow while skipping project-specific files like CLAUDE.md and sync-db.sh. - Divergence Protection: Never overwrites an existing sync-db.sh or .db-sync.env.example, since projects may have customized them; suggests diffing against templates instead. - Gitignore Maintenance: Appends only missing entries to .gitignore without duplicating existing rules. - Use Case: After upgrading the Bravros CLI, run this skill to bring an existing repository's hooks and CI workflow up to date without clobbering your customized database sync script. ## Quick Start Ask the agent to sync this project with the latest Bravros workflow files, updating hooks and the GitHub Action while preserving my existing sync-db.sh.

Frequently Asked Questions about workflow-sync

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

FAQPage Schema
How do I update git hooks and GitHub Actions in an existing Bravros project?▼

Run the workflow-sync skill, which overwrites .bravros/hooks/commit-msg, .bravros/hooks/pre-push, and .github/workflows/claude.yml with the latest versions. It uses bravros init with skip flags and copies the workflow template from ~/.bravros/templates.

What is the difference between /start and /workflow-sync?▼

The /start command performs first-time project setup without clobbering anything, while /workflow-sync updates an existing project by overwriting workflow files with the latest versions. Use workflow-sync only on projects already initialized.

Will workflow-sync overwrite my customized sync-db.sh script?▼

No, sync-db.sh and .db-sync.env.example are skipped if they already exist, since projects may have diverged with custom targets or dump flags. To adopt template improvements, diff the template against your file manually.

Does workflow-sync modify CLAUDE.md or commit changes automatically?▼

No, CLAUDE.md is always skipped because it is project-specific, and the skill never auto-commits. All changes are left for you to review before committing.

What prerequisites are needed before running workflow-sync?▼

The project must be a git repository with an existing .bravros/hooks directory, meaning it was previously initialized with Bravros. The skill verifies these prerequisites before updating any files.