Loose Ends

Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.

62 stars 2 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ElliotJLT/Claude-Skill-Potions --skill loose-ends
Manual install
git clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/loose-ends ~/.claude/skills/loose-ends

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Loose Ends

<purpose>
Implementation feels done, but loose ends remain. The import you added but didn't
use. The TODO you wrote and forgot. The test you meant to add. The console.log
you left in. This skill forces a sweep before declaring victory.
</purpose>

## When To Activate

<triggers>
- About to say "done" or "complete"
- Finishing a feature implementation
- After fixing a bug
- Before committing changes
- After any multi-file change
- User asks "is it ready?"
</triggers>

## Instructions

### The Loose Ends Checklist

Before declaring complete, run through:

<checklist>
## Loose Ends Sweep

### Code Hygiene
- [ ] No unused imports
- [ ] No unused variables
- [ ] No commented-out code (unless intentional)
- [ ] No console.log/print statements left in
- [ ] No debugger statements

### TODOs and FIXMEs
- [ ] No new TODOs created and forgotten
- [ ] Any existing TODOs in touched files addressed or noted

### Tests
- [ ] New code has tests (or explicit reason why not)
- [ ] Existing tests still pass
- [ ] Edge cases considered

### Types (if applicable)
- [ ] No `any` types added
- [ ] No type assertions without reason
- [ ] Interfaces/types defined for new structures

### References
- [ ] Old references updated if things were renamed
- [ ] No broken imports
- [ ] No stale comments referring to old code

### Error Handling
- [ ] Errors handled or explicitly bubbled up
- [ ] User-facing errors have good messages
- [ ] No silent failures
</checklist>

### Automated Sweep
Read the full skill on GitHub

Details

Skill name
loose-ends
Path
skills/loose-ends/SKILL.md
License
MIT
Repo updated
12 February 2026

FAQ

What does the Loose Ends skill do?

Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.

How do I install the Loose Ends skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill loose-ends. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Loose Ends popular?

It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.

Related skills

Agent Audit

62

ElliotJLT/Claude-Skill-Potions

When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.

AI, LLMs & Agents

Battle Plan

62

ElliotJLT/Claude-Skill-Potions

Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.

Software Development

Breadcrumbs

62

ElliotJLT/Claude-Skill-Potions

Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.

Productivity & Notes

Pipeline

62

ElliotJLT/Claude-Skill-Potions

Orchestration pattern for sequential, dependent tasks. When work must flow through stages where each stage depends on the previous (design → implement → test → review), structure as a pipeline with explicit handoffs. Each stage completes before the next begins.

Testing & QA

Fan Out

62

ElliotJLT/Claude-Skill-Potions

Orchestration pattern for parallelizable tasks. When facing work that can be split into independent subtasks (research multiple topics, analyze multiple files, test multiple scenarios), spawn parallel agents and aggregate results. Use when subtasks have no dependencies on each other.

Testing & QA

Power Calculations

36

dariia-m/my_claude_skills

Power, minimum detectable effect (MDE) and sample-size calculations in R for randomized experiments and survey experiments - two-arm and multi-arm designs with a shared control, ANCOVA vs change-score vs post-only, binary outcomes, within-subject differences, interactions/heterogeneity, clustered assignment, attrition and exclusions, and multiple-testing adjustment (per-test, Bonferroni bound, Holm/Romano-Wolf). Combines closed-form MDEs with Monte Carlo simulation of the exact pre-registered regression, including size checks. Use whenever the user asks for power calculations, an MDE table, "h

Testing & QA11

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.