ar-taskflow-progress-fixer

Reconcile task workspace artifacts against actual git and GitHub state.

1|2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-taskflow-progress-fixer-mahsanamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ar-taskflow-progress-fixer
Source: https://github.com/mahsanamin/agentic-repos/tree/main/workspace-skills/ar-taskflow-progress-fixer
Command: npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-taskflow-progress-fixer-mahsanamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Task-tracking artifacts like execution plans, summaries, and task folders drift from reality: PRs get merged but tasks are never archived, execution summaries claim no PR exists days after one opened, and declared branches do not actually exist. This Skill scans the workspace, detects these mismatches, and applies safe fixes. ## Core Features & Use Cases - Workspace Reconciliation: Runs ten checks covering phase detection, archive state, TasksSummary gaps, stale execution summaries, PR merge verification via the GitHub CLI, branch existence, and worktree mapping. - Docs-Repo Sync Gate: Verifies the workspace docs-repo is clean and in sync with origin before scanning, so checks never run on stale data. - Safe Auto-Fixes: Archives tasks whose PRs merged to main, fills completion dates from merge timestamps, and pushes docs changes, all only after explicit user approval. - Use Case: Before generating a weekly report, run a reconciliation pass to catch a task whose PR merged last week but still sits in OnGoingTasks, then archive it and backfill its completion date automatically. ## Quick Start Ask the assistant to reconcile tasks in the workspace by saying "ar-taskflow-progress-fixer" or "reconcile tasks".

Frequently Asked Questions about ar-taskflow-progress-fixer

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

FAQPage Schema
How do I find tasks that were merged but never archived?▼

Run the reconciliation scan, which queries GitHub for merged PRs matching each task's ticket ID and flags Phase 4 tasks still sitting in OnGoingTasks. Tasks whose PRs merged to main are eligible for automatic archiving after your approval.

How to verify a task's PR was actually merged on GitHub?▼

The skill extracts the ticket ID from the folder name or ticket file, then searches merged and open PRs by title using the GitHub CLI. It validates the ticket ID appears verbatim in the PR title and reports MERGED, PR_OPEN, or NO_PR states.

Does the reconciliation work with multiple platforms like Backend and Frontend?▼

Yes, it reads the platforms list from config_hints.json and derives separate OnGoingTasks, DoneTasks, and TasksSummary paths per platform. Each platform can map to its own GitHub repository for PR-merge checks.

Why does the skill stop when the docs-repo is behind origin?▼

Scanning a stale docs-repo produces false findings, such as warning about missing rows a colleague already added. The skill hard-stops when the repo is dirty, diverged, or more than five commits behind, and offers a fast-forward pull for small gaps.

Can it automatically fix a stale execution-summary file?▼

No, stale execution summaries are reported as warnings only. The file carries high-context state like Q&A logs and decisions, so the user must re-sync it manually rather than risk an automated rewrite.