Orchestrates unattended GitHub issue implementation from worktree setup through open pull request.
npx skills add https://github.com/mimukit/skills --skill afkkit-mimukit
Please help me install this Agent Skill. Skill: afkkit Source: https://github.com/mimukit/skills/tree/main/skills/afkkit Command: npx skills add https://github.com/mimukit/skills --skill afkkit-mimukit
ready issue reaches a reviewable PR with no human present, while keeping planning, review, and merge as human gates. ## Core Features & Use Cases - Unattended pipeline orchestration: Sequences companion skills (issuekit, implementkit, commitkit, reviewkit, qakit, prkit) as subagent dispatches, each running in the issue's isolated git worktree. - Escalation policy: When a step cannot proceed, it stops cleanly with no PR, keeps all commits intact, comments the precise stuck-state on the issue, and sets the label by cause (needs-planning for decision gaps, in-progress for execution gaps). - Batch mode: afkkit all drains the whole ready queue sequentially, ordered by priority labels, with one up-front confirmation and a final batch summary. - Use Case: Before leaving for the day, tell the agent to work the ready issues overnight; return to open PRs with committed QA plans, or cleanly escalated issues with exact reasons and preserved work. ## Quick Start Ask the agent to run issue #42 unattended through afkkit so it is implemented, verified, reviewed, and opened as a pull request.High-intent search queries and answers about installing and using this skill.
Invoke afkkit with the issue number, such as "afkkit 42" or "run #42 unattended". The issue must carry the ready label; the skill then drives worktree setup, implementation, verification, review, fixes, QA planning, and PR opening without further input.
Run "afkkit all" to drain the entire ready queue. It lists the issues ordered by priority labels, asks for one up-front confirmation, then runs the full pipeline on each issue sequentially and prints a batch summary at the end.
The run escalates instead of pushing forward: no PR opens, the worktree and commits stay intact, a comment on the issue names the exact stuck-state, and the label reflects the cause. Planning gaps flip to needs-planning; execution failures keep in-progress.
Yes. It requires the GitHub CLI authenticated, plus companion skills issuekit, implementkit, commitkit, reviewkit, qakit, and prkit. issuekit is mandatory with no fallback because it owns the ready-label guard the safety model depends on.
No. Planning and grilling stay interactive and happen before an issue earns the ready label, and review and merge happen after the PR opens. The skill's span ends at PR open and it never responds to PR review feedback.
beeminderGroom stale DEV-labeled issues in the beeminder/blog repository.
catu-aiMerge an approved pull request after confirming an archived harness plan.
stellaCoordinate automated PR review comments from multiple bots in a single pass.
thavirak-svayAutomate tech spec implementation through a step-by-step development workflow.