skills.rest
B0yZ4kr14
B0yZ4kr14COMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-cleanup

Reviews changed files and classifies issues after feature implementation using predefined criteria.

Updated Mar 16, 2026
Search Tags:#linting#quality gate#tech debt#issue triage#code cleanup#Specify
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-cleanup-b0yz4kr14
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-cleanup
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-cleanup
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-cleanup-b0yz4kr14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After an implementation, it helps you systematically review what changed, fix small problems immediately, create tasks for medium issues, and produce deeper analysis for large or architecture-level problems—without violating the project constitution.

Core Features & Use Cases

  • Small-issue quality gate: Detects and fixes mechanical problems (like debugging artifacts or clearly dead code) with user confirmation.
  • Medium-issue follow-ups: Classifies issues that need judgment and creates actionable items in tasks.md.
  • Large-issue tech-debt analysis: Generates tech-debt-report.md for bigger architectural, security-design, or constitution-violating concerns.

Quick Start

Run speckit-cleanup from the feature directory after your implementation tasks have completed, so it can read spec.md, plan.md, tasks.md, and constitution.md and then ask what to fix.

Frequently Asked Questions about speckit-cleanup

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

FAQPage Schema
How do I triage code cleanup tasks after finishing a feature implementation?▼

Post-implementation triage systematically reviews changed files against project rules, classifying issues into immediate mechanical fixes, actionable follow-up tasks, and large tech-debt analysis outputs.

What is the best way to detect debugging remnants and dead code before committing?▼

Detecting debugging artifacts and dead code is performed by running a quality gate check that compares recent feature changes against configured linting guidance and the project constitution.

How does a quality gate handle large architecture-level tech debt?▼

A quality gate handles large architecture-level tech debt by generating a dedicated tech-debt-report.md, isolating major constitution-violating concerns from immediate mechanical fixes.

Do I need a .specify directory structure to run issue triage on my code?▼

Yes, issue triage requires a .specify directory structure to read spec.md, plan.md, tasks.md, and constitution.md, deriving the necessary feature directory context for accurate quality checks.

Can I automatically fix code cleanup issues without manual review?▼

No, code cleanup actions are gated with user confirmation, ensuring mechanical fixes like dead-code removal are explicitly approved before modifying files or updating tasks.md.

Related Skills

Explore More Software Engineering Skills→
jineynejineyne

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for cross-artifact inconsistencies and coverage gaps.

Community
Advanced
datamonsterrdatamonsterr

speckit-cleanup

Review completed spec-kit changes and generate a tech-debt-report with follow-up tasks.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
huangzidahuangzida
2

triage

Categorize issues into canonical roles and states via a state-machine workflow.

Community
Advanced