gxpm-cleanup

Consolidate cross-issue code quality debt and generate a cleanup-report artifact.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gxpm-cleanup
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-cleanup
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The gxpm-cleanup skill identifies and consolidates cross-issue code quality debt during the cleanup phase, ensuring the codebase is unified before a ship transition.

Core Features & Use Cases

  • Detect cross-issue duplicates and dead code across multiple worktrees.
  • Unify naming, align interfaces, and prune redundant tests before ship.
  • Use case: when handling 2+ issues in a single worktree, run cleanup to produce a clean, auditable cleanup-report artifact.

Quick Start

Run gxpm self-review cleanup <issue-id> to initialize the cleanup workflow and draft the cleanup-report artifact.

Frequently Asked Questions about gxpm-cleanup

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

FAQPage Schema
How do I consolidate duplicate code and dead code across multiple issues before shipping?▼

You consolidate cross-issue code quality debt by running a cleanup workflow that detects duplicates, unifies naming, aligns interfaces, and removes dead code. It produces an auditable cleanup-report artifact for a reproducible ship transition.

What is cross-issue code quality debt and when do I need to clean it up?▼

Cross-issue code quality debt consists of duplicates, misaligned interfaces, and dead code generated when resolving multiple issues in one worktree. You need cleanup during the transition from self-review to ship to ensure a unified, auditable codebase.

Can I run code cleanup if some issues in my worktree haven't reached self-review yet?▼

No, you cannot run cleanup if issues haven't reached self-review. The workflow requires all issues in the worktree to reach self-review prior to cleanup, ensuring the codebase is stable enough for cross-issue consolidation and interface alignment.

How do I deduplicate redundant tests across multiple worktrees before a ship transition?▼

You deduplicate redundant tests by running a cleanup workflow that extracts duplicates and unifies naming across issues. This generates a testsDeduplicated record within the cleanup-report artifact to enable an auditable, reproducible ship transition.

What is the best way to align interfaces and unify naming conventions across multiple resolved issues?▼

The best way to align interfaces and unify naming is to execute a cross-issue cleanup workflow. It applies when multiple issues exist in a worktree, generating a cleanup-report with renamesUnified and interfacesAligned records for an auditable transition.

Does the cleanup workflow generate an artifact for auditing codebase transitions?▼

Yes, the cleanup workflow generates a cleanup-report artifact containing records like duplicatesExtracted, renamesUnified, interfacesAligned, deadCodeRemoved, and testsDeduplicated. This enables auditable, reproducible transitions per core phase-gates rules.