mg-tidy

Reconcile GitHub issues with memory state using the gh CLI.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-tidy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mg-tidy
Source: https://github.com/wonton-web-works/miniature-guacamole/tree/main/src/framework/skills/mg-tidy
Command: npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-tidy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconciles project state across GitHub issues and memory files, deduplicating duplicate issues, aligning memory with live workstreams, and generating canonical state reports to keep programs on track.

Core Features & Use Cases

  • Audit-first reconciliation: compares GitHub issues with memory state to surface drift.
  • Duplicate management: closes only confirmed duplicates and preserves the highest-numbered issue.
  • Memory health & reporting: detects orphans, creates missing memory stubs, and produces a unified state report.

Quick Start

Run mg-tidy to audit your GitHub issues and memory state and start reconciliation.

Frequently Asked Questions about mg-tidy

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

FAQPage Schema
How do I reconcile GitHub issues with local memory state to detect project drift?

To reconcile GitHub issues with memory state, mg-tidy audits your project governance data using the gh CLI, detects drift between live workstreams and memory files, and generates a canonical state report to keep programs aligned.

What is the best way to detect and close duplicate GitHub issues during memory reconciliation?

The best way to manage duplicate GitHub issues during memory reconciliation is to run an audit-first process that closes only confirmed duplicates while preserving the highest-numbered issue, aligning memory with live workstreams.

Can I use gh CLI to audit GitHub issue health and detect orphaned memory files?

Yes, you can use gh CLI to perform audit-first reconciliation that detects orphaned memory files, creates missing memory stubs for issues, and produces a unified state report to drive project governance and planning.

Do I need to run preflight checks before reconciling GitHub issues with memory state?

Yes, preflight checks are required before reconciling GitHub issues with memory state to ensure memory consistency, verify issue health, and safely execute deduplication and reconciliation operations using the gh CLI.

Why does my project memory state drift from live GitHub issues over time?

Project memory state drifts from live GitHub issues due to untracked workstream updates and duplicate issue creation, requiring an audit-first reconciliation to detect orphans, update memory stubs, and enforce a canonical project view.