polish-all

Name: polish-all
Availability: InStock
Author: guarzo

Automate codebase polishing across architecture-aligned segments with checkpointed progress.

Updated Mar 25, 2026

Search Tags:#automation #codebase #checkpoints #review #diff #polish

Ready to run

npx skills add https://github.com/guarzo/slabledger --skill polish-all

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: polish-all
Source: https://github.com/guarzo/slabledger/tree/main/.claude/skills/polish-all
Command: npx skills add https://github.com/guarzo/slabledger --skill polish-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a comprehensive, non-interactive codebase polish process across architecture-aligned segments, collecting findings and applying safe auto-fixes while maintaining an auditable trail.

Core Features & Use Cases

Systematic health checks across each segment using an improve workflow with checkpointed progress.
Diff-based polishing with auto-fixes applied per segment, with results accumulated into the central report.
Segment-level resume and isolation, enabling restart after interruptions and easier auditing.
Centralized outputs in docs/polish-progress.json and docs/polish-report.md for traceability.

Quick Start

Run the polish-all skill to start a complete, checkpointed polish pass across all 12 segments.

Frequently Asked Questions about polish-all

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

FAQPage Schema

How do I automate codebase polishing across architecture-aligned segments?▼

Automate codebase polishing by running an end-to-end process that applies health checks and diff-based polish passes per segment, accumulating safe auto-fixes and findings into a centralized markdown report and JSON progress file.

What is the best way to run a non-interactive code review with auto-fixes?▼

Run a non-interactive code review using an automated diff-based polish pass that applies safe auto-fixes per segment, ensuring an auditable trail by accumulating results into a central report without requiring manual intervention.

Do I need a Git repository to run an automated code polish and health check?▼

Yes, you need a Git repository to run the automated code polish and health check, because the skill relies on Git diffs to identify changes and apply auto-fixes across architecture-aligned segments.

How does checkpointed progress work when polishing a large codebase?▼

Checkpointed progress saves polishing state to a JSON file per segment, enabling segment-level resume and isolation so you can easily restart the process after interruptions without losing previous findings.

Where are the findings and auto-fixes stored after an automated codebase polish?▼

Findings and auto-fixes from the automated codebase polish are stored as centralized outputs in docs/polish-progress.json for traceability and docs/polish-report.md for readable reporting.

Can I resume a codebase health check if the automated polishing process is interrupted?▼

Yes, you can resume an interrupted codebase health check because the automated polishing process uses segment-level isolation and checkpoints, allowing you to restart from the last saved progress without losing accumulated results.