Sync
A command for orchestration workflows.
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/commands/orchestration/sync.md
# Orchestration Sync Command
Synchronize task status with git commits, ensuring consistency between version control and task tracking.
## Usage
```
/orchestration/sync [options]
```
## Description
Analyzes git history and task status to identify discrepancies, automatically updating task tracking based on commit evidence and maintaining bidirectional consistency.
## Basic Commands
### Full Sync
```
/orchestration/sync
```
Performs complete synchronization between git and task status.
### Check Sync Status
```
/orchestration/sync --check
```
Reports inconsistencies without making changes.
### Sync Specific Orchestration
```
/orchestration/sync --date 03_15_2024 --project auth_system
```
## Sync Operations
### Git → Task Status
Updates task status based on commit messages:
```
Found commits:
- feat(auth): implement JWT validation (TASK-003) ✓
Status: in_progress → qa (based on commit)
- test(auth): add JWT validation tests (TASK-003) ✓
Status: qa → completed (tests indicate completion)
- fix(auth): resolve token expiration (TASK-007) ✓
Status: todos → in_progress (work started)
```
### Task Status → Git
Identifies tasks marked complete without commits:
```
Status Discrepancies:
- TASK-005: Marked 'completed' but no commits found
- TASK-008: In 'qa' but no implementation commits
- TASK-010: Multiple commits but still in 'todos'
```
## Detection Patterns
### Commit Pattern Matching
```
Patterns detected:
- "feat(auth): implement" → Implementation complete
- "test(auth): add" → Testing phase
- "fix(auth): resolve" → Bug fix complete
- "docs(auth): update" → Documentation done
- "refactor(auth):" → Code improvement
```
### Task Reference Extraction
```
Scanning commits for task references:
- Explicit: "Task: TASK-003" ✓
- In body: "Implements TASK-003" ✓
- Branch name: "feature/TASK-003-jwt" ✓
- PR title: "TASK-003: JWT implementation" ✓
```
## Sync Rules
### Automatic Status Updates
```yaml
sync_rules:
commit_patterns:
- pattern: "feat.*TASK-(\d+)"
action: "move to qa if in_progress"
- pattern: "test.*TASK-(\d+).*pass"
action: "move to completed if in qa"
- pattern: "fix.*TASK-(\d+)"
action: "move to qa if in_progress"
- pattern: "WIP.*TASK-(\d+)"
action: "keep in in_progress"
```
### Conflict Resolution
```
Conflict detected for TASK-003:
- Git evidence: 3 commits, tests passing
- Task status: in_progress
- Recommended: Move to completed
Resolution options:
[1] Trust git (move to completed)
[2] Trust tracker (keep in_progress)
[3] Manual review
[4] Skip
```
## Analysis Reports
### Sync Summary
```
Synchronization Report
======================
Analyzed: 45 commits across 3 branches
Tasks referenced: 12
Status updates needed: 4
Updates to apply:
- TASK-003: in_progress → completed (3 commits)
- TASK-007: todos → in_progress (1 commit)
- TASK-009: qa → completed (tests added)
- TASK-011: on_hold → in_progress (blocker resolved)
Warnings:
- TASK-005: Completed without commits
- TASK-013: Commits without task reference
```
### Detailed Analysis
```
Task: TASK-003 - JWT Implementation
Current Status: in_progress
Git Evidence:
- feat(auth): implement JWT validation (2 days ago)
- test(auth): add validation tests (1 day ago)
- fix(auth): handle edge cases (1 day ago)
Recommendation: Move to completed
Confidence: High (95%)
```
## Options
### Dry Run
```
/orchestration/sync --dry-run
```
Shows what would change without applying updates.
### Force Sync
```
/orchestration/sync --force
```
Applies all recommendations without prompting.
### Time Range
```
/orchestration/sync --since "1 week ago"
```
Only analyzes recent commits.
### Branch Specific
```
/orchestration/sync --branch feature/auth
```
Syncs only tasks related to specific branch.
## Integration Features
### Update Tracking Files
```
/orchestration/sync --update-trackers
```
Updates TASK-STATUS-TRACKER.yaml with:
```yaml
git_tracking:
TASK-003:
status_from_git: completed
confidence: 0.95
evidence:
- commit: abc123
message: "feat(auth): implement JWT"
date: "2024-03-13"
- commit: def456
message: "test(auth): add tests"
date: "2024-03-14"
```
### Generate Commit Report
```
/orchestration/sync --commit-report
```
Creates report of all task-related commits.
### Fix Orphaned Commits
```
/orchestration/sync --link-orphans
```
Associates commits without task references.
## Sync Strategies
### Conservative
```
/orchestration/sync --conservative
```
Only updates with high confidence matches.
### Aggressive
```
/orchestration/sync --aggressive
```
Updates based on any evidence.
### Interactive
```
/orchestration/sync --interactive
```
Prompts for each potential update.
## Examples
### Example 1: Daily Sync
```
/orchestration/sync --since yesterday
Quick sync results:
- 5 commits analyzed
- 2 tasks updated
- All changes applied successfully
```
### Example 2: Branch Merge Sync
```
/orchestration/sync --after-merge feature/auth
Post-merge sync:
- 15 commits from feature/auth
- 5 tasks moved to completed
- 2 tasks have test failures (kept in qa)
```
### Example 3: Audit Mode
```
/orchestration/sync --audit --report
Audit Report:
- Tasks with commits: 85%
- Commits with task refs: 92%
- Average commits per task: 2.3
- Orphaned commits: 3
```
## Webhook Integration
### Auto-sync on Push
```yaml
git_hooks:
post-commit: /orchestration/sync --last-commit
post-merge: /orchestration/sync --branch HEAD
```
## Best Practices
1. **Regular Syncs**: Run daily or after major commits
2. **Review Before Force**: Check dry-run output first
3. **Maintain References**: Include task IDs in commits
4. **Handle Conflicts**: Don't ignore sync warnings
5. **Document Decisions**: Note why status differs from git
## Configuration
### Sync Preferences
```yaml
sync_config:
auto_sync: true
confidence_threshold: 0.8
require_tests: true
trust_git_over_tracker: true
patterns:
- implementation: "feat|feature"
- testing: "test|spec"
- completion: "done|complete|finish"
```
## Notes
- Requires git access to all relevant branches
- Preserves manual status overrides with flags
- Supports custom commit message patterns
- Integrates with CI/CD for automated syncingPreview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: 18b34621dab9ea2515f58172faf54baa636fe370a8bdce49d84c4fc7c1aab91d. Files are served as downloads and are never executed by this page.