// Sync commits to both main and v0/rohangupta-dec27c78 branches. Use after committing changes, when pushing code, or when asked to sync branches. Ensures both branches stay in lockstep.
Create a new documentation page for the Harness 3.0 docs site. Use when adding a new doc page, creating documentation, or when asked to add a page to the docs. Handles all three required file registrations and generates the page component.
Validate documentation pages against project conventions. Use when checking if doc pages are correctly set up, debugging broken navigation, or before committing doc changes. Checks all three registration points, TOC consistency, section IDs, and YAML schema compliance.
Reference guide for Harness 3.0 documentation site conventions, component patterns, and styling rules. Auto-invoked when working on documentation pages, editing components in docs/pages/, or modifying docs-data.ts. Use explicitly to look up the correct pattern for a specific UI element.
| name | sync-branches |
| description | Sync commits to both main and v0/rohangupta-dec27c78 branches. Use after committing changes, when pushing code, or when asked to sync branches. Ensures both branches stay in lockstep. |
| disable-model-invocation | true |
| allowed-tools | Bash(git *) |
After committing changes, sync them to both main and v0/rohangupta-dec27c78 branches. Both branches MUST always stay in sync.
Confirm current state
git status to ensure the working tree is cleangit log --oneline -3 to identify the commit(s) to syncIf on main:
git checkout v0/rohangupta-dec27c78
git cherry-pick <commit-hash>
git checkout main
If on v0/rohangupta-dec27c78:
git checkout main
git cherry-pick <commit-hash>
git checkout v0/rohangupta-dec27c78
Push both branches:
git push origin main
git push origin v0/rohangupta-dec27c78
Return to the original branch the user was on.