Detect drift between wiki tasks and Asana, Jira, and GitHub backends.
npx skills add https://github.com/brandtam/rubber-ducky --skill reconcile-brandtam
Please help me install this Agent Skill. Skill: reconcile Source: https://github.com/brandtam/rubber-ducky/tree/main/src/skills/reconcile Command: npx skills add https://github.com/brandtam/rubber-ducky --skill reconcile-brandtam
Reconcile drift between the wiki and its linked backends, surface it to the User per ticket, and let the User resolve it via four moves.
Start a reconciliation by detecting drift and presenting drifted tickets for guided resolution.
High-intent search queries and answers about installing and using this skill.
Wiki-backend drift is detected by reading and aggregating deltas between the wiki and linked backends, then surfacing per-ticket field diffs for user review. You resolve surfaced drift using a guided four-move workflow: Accept Asana, Accept Jira, Accept Wiki, or Skip.
Yes, task tracking data from Asana, Jira, and GitHub is synchronized by merging backend deltas with wiki entries to highlight drift. The workflow operates in two phases: phase one aggregates drift read-only, and phase two enforces token-validated transitions for resolution.
The best way to reconcile task tracking discrepancies is per-ticket drift detection that merges wiki, Asana, and Jira deltas to highlight field-level diffs. This surfaces exact discrepancies for guided resolution through four defined moves per ticket.
Yes, the workflow supports a read-only description-drift detection phase before applying changes. This first phase reads and aggregates drift across backends, surfacing per-ticket diffs for review before prompting token-validated transitions in the second phase.
Per-field differences are reviewed through per-ticket views that merge wiki, Asana, and Jira deltas to highlight drift. These views surface specific field diffs, allowing you to choose one of four resolution moves to reconcile each ticket individually.
Automated wiki-backend drift resolution does not auto-correct data; it surfaces per-ticket drift and per-field diffs for manual user review. Limitations include requiring user intervention to select one of four moves, ensuring changes are token-validated rather than fully autonomous.
brandtamDraft a closing comment, update wiki status, and transition linked backends.
brandtamPost comments to external tickets via rubber-ducky CLI using wiki backend references.
anhhung04Automate task creation and status updates from GitHub issues via the API.
brandtamTriage untriaged Asana intake pages into Jira tickets, not-needed, or skip.
