Skip to content
Back to skills

Do

ASecurity

Work through a TODO.md checklist in the worktree root, continuing until all items are checked off.

  • 17 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 17, 2026
ai-agentsbashgit

Works with

  • claude code

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 17, 2026

npx -y skills add chardigio/pappardelle --skill do --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Do?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Do
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/chardigio-pappardelle/badge)](https://www.skillsdirectory.com/skills/chardigio-pappardelle)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: do
description: Work through a TODO.md checklist in the worktree root, continuing until all items are checked off.
disable-model-invocation: true
---

# /do - Work Through TODO Checklist

## Setup

Before doing anything else, copy the TODO template into the worktree root (always overwrite — keeps a single canonical seed step that runs on every invocation):

```bash
cp .claude/skills/do/TODO-TEMPLATE.md TODO.md
```

Then read `TODO.md` — a checklist of tasks to complete for this issue — and work through every item systematically.

## How It Works

1. **Read `TODO.md`** to see what needs to be done
2. **Work through each item** in order
3. **Check off items** as you complete them by marking each empty checkbox as done and adding a detailed explanation of what was done and how in parentheses after.

## Rules

- Always check off an item (`- [x]`) immediately after completing it
- Work through items in order unless dependencies require a different sequence
- If an item is blocked or not applicable, check it off and add a note explaining why
- Use `AskUserQuestion` when requirements are ambiguous or you need user input
- Make small, incremental changes and test frequently

## Updating Issue Details

When you start working on an issue, update it with proper details:

### 1. Assign to the Correct Project

The issue may not have a project assigned yet. Based on what you're implementing, assign it to the appropriate project.

### 2. Update Title (if needed)

If the auto-generated title isn't ideal, improve it to clearly describe the task.

### 3. Update Description

Update the description but **keep the "Original prompt" section at the bottom**:

```
Your detailed description here...

---

_Original prompt:_

> <keep the original prompt text as a blockquote>
```

### 4. Update GitHub PR

Edit the PR body to add summary details, but **preserve the "Original prompt" section**:

```bash
gh pr edit --body "## Summary
- Bullet points describing changes

## Test plan
- How to test

## Issue
[Link to issue]

---

_Original prompt:_

> <keep the original prompt text as a blockquote>

---
Generated with [Claude Code](https://claude.com/claude-code)"
```

## Argument

The argument passed to this skill is the issue key (e.g., `PROJ-123`). Use it for:

- Looking up the issue in your issue tracker
- Updating issue status as you progress
- Commit messages: `[PROJ-123] Description`

Files in this skill

  • README.md1.1 KB
  • SKILL.md2.4 KB
  • TODO-TEMPLATE.md1.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.