midnite-address-issue

Triages GitHub issue boards, fixes the chosen issue in a worktree, and opens a linked pull request.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-address-issue-bilo-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: midnite-address-issue
Source: https://github.com/bilo-io/midnite-studio/tree/main/.agents/skills/midnite-address-issue
Command: npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-address-issue-bilo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual overhead of picking the highest-impact issue from a backlog, reproducing the bug, planning a fix, and shipping it as a reviewed pull request for the Midnite Studio repository. ## Core Features & Use Cases - Dual-board triage: Scans both the internal engineering backlog and the public user-facing issue board, filters out claimed or already-fixed items, and scores candidates by correctness impact, blast radius, and fix cost. - Interactive planning gates: Stops for human approval when choosing the issue and when agreeing the fix plan, then runs autonomously through reproduction, root-cause analysis, test-first implementation, and PR creation. - Worktree lifecycle management: Builds the fix in an isolated git worktree with a handover scratchpad, drives CI green, watches for the merge, and sweeps landed worktrees to reclaim disk. - Use Case: A maintainer invokes the skill with no arguments; it digests 50 open issues across both boards, recommends the highest-impact bug with three alternatives, and after approval delivers a draft PR with a regression test and before/after screenshots. ## Quick Start Invoke the midnite-address-issue skill, optionally passing an issue number, label, or keyword, and let it triage the boards and propose four candidate issues to fix.

Frequently Asked Questions about midnite-address-issue

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

FAQPage Schema
How do I automatically triage and fix GitHub issues with an AI agent?▼

Invoke the skill with an optional issue number, label, or keyword. It lists open issues from both boards, scores them by impact and fix cost, presents four options for you to pick, then reproduces, fixes, and opens a linked draft PR.

Does the skill merge pull requests automatically?▼

No, it never merges on its own. It stops after opening the PR and arms a background watcher; only when the human merges does it run the post-merge wrap-up comment, changelog entry, and worktree teardown.

Can it handle issues reported in a different GitHub repository?▼

Yes, it scans the public bilo-io/midnite-apps board with explicit -R flags on every gh call. PRs use the cross-repo closing keyword Fixes bilo-io/midnite-apps#N so user-filed reports auto-close on merge.

What happens if the root cause of a bug cannot be found?▼

The skill stops and reports what it ruled out instead of guessing a fix. It treats a wrong fix on a public issue as worse than an honest request for more investigation.

How does it prevent losing work when a session dies mid-fix?▼

Each worktree keeps an untracked SCRATCHPAD.md recording decisions, progress, and the next step. A new run checks for abandoned scratchpads and asks whether to resume that worktree or start fresh.

When should I not use this issue-fixing workflow?▼

Avoid it for issues needing a product decision the agent cannot make, cosmetic-only nits, or bugs whose root cause cannot be located in the triage pass. Those are deprioritized or escalated to the human during scoring.