afk-pickup

Picks the next eligible AFK-labeled GitHub issue and dispatches autonomous work on it.

1|1|Updated Oct 3, 2021
One-click install
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill afk-pickup-benjr70
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: afk-pickup
Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/afk-pickup
Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill afk-pickup-benjr70

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running an autonomous coding agent on a schedule requires deciding, on every fire, what to work on: an open agent PR needing reconciliation, a paused issue to resume, or the next prioritized backlog item. Doing this triage by hand each time is slow and error-prone. ## Core Features & Use Cases - One-call triage: A single read-only script evaluates the concurrency lock, open PRs needing attention (conflicts, AFK:revise hand-backs, incomplete bot tails, docs-only merges, Dependabot bumps), paused issues, and the project backlog pick. - Priority-aware picking: Selects the highest-Priority, oldest AFK-labeled issue from the Smart Smoker V2 GitHub Project with native blockedBy dependencies resolved and no human assignee. - Routing and dispatch: Resumes paused work preserving its branch, routes wayfinder Decision tickets to /afk-resolve, merges docs-only and Dependabot PRs through validated gate commands, and dispatches everything else to /afk-dispatch. - Use Case: A cron-fired Claude routine runs /afk-pickup every window; it reconciles a conflicting PR if one exists, otherwise picks issue #142 (P0, unblocked) and spawns the implementation team, opening a PR on success. ## Quick Start Run /afk-pickup to triage the repository and autonomously pick up the next eligible GitHub issue, or use /afk-pickup --dry-run to preview the pick without mutating anything.

Frequently Asked Questions about afk-pickup

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

FAQPage Schema
How do I autonomously pick the next GitHub issue for an AI agent?

Run /afk-pickup with no arguments. It triages open PRs, paused issues, and the project backlog in one read-only script call, then dispatches the winner to /afk-dispatch or /afk-resolve. Use --dry-run to preview the pick without changes.

How does the picker decide which issue is eligible?

An issue must be open, carry the AFK label, belong to the Smart Smoker V2 GitHub Project, lack AFK:in-progress/done/failed labels, have all native blockedBy dependencies closed, and have no human assignee. Highest Priority field wins, then oldest createdAt.

What happens when an open agent PR has a merge conflict?

A conflicting agent PR outranks any new pick. The skill locks the backing issue, spawns the /pr-reconcile skill to fix the conflict, restores the lock, and exits without picking new work.

Can it run when the gh token lacks the project scope?

Yes. When gh is unauthenticated or missing the project scope, the skill falls back to the GitHub MCP GraphQL tools and applies the same query, filters, and wayfinder routing rules by hand.

What happens to an issue paused too many times?

When a paused issue hits the resume cap, the skill removes AFK:paused, applies AFK:failed, posts a comment explaining the cap was reached, and exits so a human can triage the oversized issue.

How are Dependabot PRs handled differently from agent PRs?

Dependabot PRs rank below every agent PR reason and dispatch to the /deps-land lane instead of /pr-reconcile. The merge only happens after deps-gate.sh approves, and the merge command is validated against a strict regex before execution.