punch-list

Group small independent maintenance changes into a verified chore workflow.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mckissinger/keel --skill punch-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: punch-list
Source: https://github.com/mckissinger/keel/tree/main/skills/punch-list
Command: npx skills add https://github.com/mckissinger/keel --skill punch-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the overhead of handling many small, independent code maintenance tasks by grouping them into a disciplined batch workflow instead of managing each change separately.

Core Features & Use Cases

  • Scoped Chore Batching: Converts scattered cleanup requests, lint fixes, typos, renames, accessibility tweaks, stale comments, and dependency updates into checkable done-conditions.
  • Parallel Task Execution: Organizes independent work into isolated subagent tasks while preventing scope creep and file collisions.
  • Use Case: A team can combine dozens of minor review comments and maintenance fixes into one verified chore pull request with a single batch verification record.

Quick Start

Use the punch-list skill to gather my small independent maintenance tasks, define their done-conditions, and prepare a verified chore workflow.

Frequently Asked Questions about punch-list

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

FAQPage Schema
How do I batch small code maintenance tasks into a single pull request?

Batch small code maintenance tasks into a single pull request by grouping scattered cleanup requests, lint fixes, and renames into a disciplined chore workflow with scoped task definitions, isolated execution, and verification checks before merging.

What is the best way to handle multiple independent lint fixes and typo corrections without managing each separately?

Handling multiple independent lint fixes and typo corrections is best achieved through scoped chore batching, which organizes independent work into isolated subagent tasks to prevent scope creep and file collisions while preparing a single verified batch pin record.

When do I need a batch verification record for chore pull requests?

You need a batch verification record for chore pull requests when merging grouped maintenance changes like dependency updates and accessibility improvements, ensuring all isolated subagent tasks meet defined done-conditions before the final merge.

Can I combine dependency updates and stale comment cleanup into one verified chore workflow?

Yes, you can combine dependency updates and stale comment cleanup into one verified chore workflow by defining scoped tasks with checkable done-conditions, executing them in parallel as isolated subagents, and verifying them before merging.

Does parallel task execution for code maintenance prevent file collisions across isolated subagents?

Parallel task execution for code maintenance prevents file collisions across isolated subagents by organizing independent work into controlled batches, stopping scope creep, and requiring verification checks before creating a single batch pin record.

Why should I not use batch chore workflows for software changes that require design decisions?

You should not use batch chore workflows for changes requiring design decisions because this process is strictly built for independent software maintenance tasks like lint fixes and renames that need isolated execution and verification without feature planning.