skills.rest
brandtam
brandtamCOMMUNITY
Explore all skills by this author →
𝕏@brandtamGitHub

reconcile

Detect drift between wiki task pages and Asana or Jira backends and apply user-chosen resolutions.

2|1|Updated Apr 12, 2026
Search Tags:#drift detection#obsidian#jira#wiki#asana#reconcile#task sync
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill reconcile-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reconcile
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/src/skills/reconcile
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill reconcile-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Task trackers and a local markdown wiki drift out of sync when teammates update Asana or Jira directly, leaving the wiki stale and untrustworthy as a source of truth. ## Core Features & Use Cases - Drift Detection: Runs dry-run pulls against Asana, Jira, and GitHub in parallel, then merges per-field deltas into a 3-way view (wiki, Asana, Jira) for every active task. - Four Resolution Moves: Per ticket, the user picks Accept Asana, Accept Jira, Accept Wiki, or Skip; writes go through confirm-token-gated pull and transition CLI calls. - Use Case: During a morning ritual, run reconcile to find that Jira moved a ticket to in-review overnight while the wiki still says in-progress, then accept Jira so the wiki and Asana are pushed to match. ## Quick Start Ask the assistant to run reconcile and check whether the wiki is in sync with Asana and Jira.

Frequently Asked Questions about reconcile

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

FAQPage Schema
How do I sync a markdown wiki with Asana and Jira?▼

Run the reconcile workflow, which dry-run pulls both backends, builds a 3-way per-field view of wiki, Asana, and Jira values, and presents drifted tickets one at a time. You then accept one side or skip, and the CLI pushes status transitions to keep all three aligned.

How does drift detection work across multiple task trackers?▼

Each backend pull returns per-field deltas with before and after values. The skill merges the Asana and Jira delta lists by file into a 3-way view; a ticket has drift when any field differs across the wiki, Asana, and Jira values.

Can reconcile update task descriptions automatically?▼

No. Description drift is reported with length and hash envelopes only, and no resolution move writes the body. You must open the backend task and wiki page side by side and merge the description manually.

What happens to tasks that only have a GitHub reference?▼

GitHub has no pull capability, so those pages are reported once as capability-skipped and drift detection is unavailable for them. Pages with both a GitHub ref and an Asana or Jira ref are reconciled through the supported backend.

Can I skip a drifted ticket permanently?▼

No. Skip issues no CLI calls and stores nothing, so the drift re-surfaces on the next reconcile run. There is deliberately no skip-with-memory or suppression list.

Related Skills

Explore More Software Engineering Skills→
brandtambrandtam
2

reconcile

Detect drift between wiki task pages and Asana or Jira backends and apply user-chosen resolutions.

Community
Advanced
brandtambrandtam
2

close

Closes tasks by drafting resolution comments, syncing backends, and updating wiki status.

Community
Advanced
brandtambrandtam
2

good-morning

Generates a prioritized morning brief from Obsidian vault tasks and daily pages.

Community
Advanced
brandtambrandtam
2

push

Push wiki task pages to external ticket backends with confirmation gating and audit logging.

Community
Advanced