skills.rest
neon-law-foundation
neon-law-foundationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

prompt-cleanup

Reconciles prompt backlog with git history and removes shipped work items.

Updated Aug 27, 2026
Search Tags:#workflow#prompts#recommendation#git history#prompt review#commit log#backlog cleanup
One-click install
npx skills add https://github.com/neon-law-foundation/navigator --skill prompt-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt-cleanup
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/prompt-cleanup
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill prompt-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps a gitignored prompts backlog accurate by checking which kickoff briefs still represent unfinished work and which ones have already shipped.

Core Features & Use Cases

  • Review against history: Reads every prompt brief and compares its completion criteria with recent git commits.
  • Retire finished prompts: Deletes prompts that are fully landed, while preserving partial or not-started briefs for later.
  • Handle ordered backlogs: Understands prompt dependencies and recommends the best next prompt to run after cleanup.
  • Use case: After a development sprint, use this Skill to remove obsolete briefs, trim multi-prompt files, and identify the highest-value next task.

Quick Start

Ask the assistant to clean up the prompts folder, verify completion against git history, delete finished prompts, and recommend the next prompt to work on.

Frequently Asked Questions about prompt-cleanup

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

FAQPage Schema
How do I clean up a prompt backlog against git commit history?▼

To clean up a prompt backlog against git commit history, you review each brief's completion criteria against recent commits, safely delete fully shipped prompts, and preserve partial or not-started briefs for later execution.

What is the best way to remove shipped prompts from a multi-prompt markdown file?▼

Removing shipped prompts from a multi-prompt markdown file requires inspecting the commit log to verify completion, trimming landed briefs from the file, and preserving incomplete prompts for the next development sprint.

How do I find the best next prompt to work on after a development sprint?▼

Finding the best next prompt after a sprint requires an ordered cleanup workflow that understands prompt dependencies, prunes finished briefs, and recommends the highest-value next task from the remaining backlog.

Can I use this prompt review process with a gitignored prompts folder?▼

Yes, prompt review applies directly to gitignored prompts folders by reconciling the backlog against git history, ensuring finished briefs are deleted while partial work remains safely stored for later.

How does the backlog cleanup process judge if a prompt is fully shipped?▼

Backlog cleanup judges if a prompt is fully shipped by applying conservative completion judgment, requiring commit-log inspection to verify the brief's completion criteria are fully met before safe deletion occurs.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
dgowriedgowrie

work-next-task

Select and complete the next unblocked task from tasks.json, updating progress.md.

Community
Intermediate
sunLeeesunLeee

check-commit-message

Validate Git commit messages against Conventional Commits rules.

Community
Intermediate
mazen160mazen160
13

backlog-loop

Enforce single backlog task completion through implementation, verification, and Judge approval.

Community
Advanced