Ships small single-commit changes through a minimal branch, test, review, and auto-merge PR workflow.
npx skills add https://github.com/Arasz/ai-badger --skill quick-task-arasz
Please help me install this Agent Skill. Skill: quick-task Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/quick-task Command: npx skills add https://github.com/Arasz/ai-badger --skill quick-task-arasz
task pipeline. - Reduced-ceremony workflow: A three-to-six bullet plan, a branch cut from fresh main, touched-surface tests only, lint and docs gates, one focused pre-push review, and a single conventional commit. - Auto-merge delivery: The PR is opened with auto-merge enabled so green CI merges without waiting for a reviewer, while red CI blocks the merge until fixed. - Use Case: A developer needs to bump a dependency and fix a lint warning. They confirm the five shape questions, cut a branch, make the change with its tests in one commit, open a PR with auto-merge, and report the merged PR with the untested surfaces named. ## Quick Start Ask the agent to handle this small fix as a quick-task: state the one-sentence change, confirm it touches a single surface, and have it branch from fresh main, test, and open an auto-merge PR with one commit.High-intent search queries and answers about installing and using this skill.
Use the quick-task workflow: confirm the change fits one sentence, one surface, and one commit, then branch from fresh main, run only the touched-surface tests plus lint and docs gates, do one focused review, and open a PR with auto-merge enabled.
Escalate when any shape question fails: the change spans multiple surfaces or layers, needs more than one commit, involves stateful or irreversible effects, requires a design decision, or the plan exceeds six bullets. Discovered breakage outside the touched surface also triggers escalation.
Yes. The pre-push focused review serves as the review, and auto-merge is enabled at PR open so all-green CI merges automatically. Red CI still blocks the merge until the branch is fixed; rules are never overridden for a failing run.
Only when the repository has no auto-bump chain such as release-please or semantic-release. If an automated chain owns VERSION, skip the manual bump and note that in the PR body, since a hand bump would collide with the chain.
Running the full suite for a single-surface change hides the touched-surface signal and defeats the fast lane's purpose. If a full suite or e2e run is genuinely required, the change is bigger than the quick-task shape and should escalate to the full task pipeline.
alex-jordan547Assess issues and pull requests, verify claims, and prepare actionable implementation briefs.
Norfolk-GroupExecute plan documents or work prompts through phased implementation, testing, and shipping workflows.
AraszCoordinates parallel agent sessions over a project message bus with broadcast events and ack discipline.
beyondwenGenerate implementation plans with tasks, files, tests, and documentation from specifications.