One-click install
npx skills add https://github.com/thtskaran/claude-skills --skill deslop-thtskaran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/thtskaran/claude-skills/tree/main/deslop
Command: npx skills add https://github.com/thtskaran/claude-skills --skill deslop-thtskaran

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

deslop helps you turn brittle, AI-generated, or “vibe-coded” projects into codebases that are safer, more resilient, and closer to production readiness by performing a structured audit and then applying fixes in a safety-ordered way.

Core Features & Use Cases

  • Two-phase workflow (audit then fix): Phase 1 generates a structured AUDIT.md with machine-parseable findings, and Phase 2 consumes that file to apply fixes safely.
  • Production hardening without changing business logic: Focuses on robustness, maintainability, security hygiene, and error handling rather than redesigning how the product works.
  • Language-agnostic, stack-aware auditing: Reconstructs the codebase map, scans patterns for consistency and quality, traces critical paths for resilience, and evaluates common security issues (OWASP Top 10 style).
  • Safety-tiered change protocol: Uses fix tiers and explicit guardrails (e.g., Tier 3 requires user approval; Tier 2 requires characterization tests).

Quick Start

Use deslop when you want to review, audit, harden, refactor safely, or fix quality issues across an existing codebase directory (you provide the path, and the skill produces AUDIT.md first, then waits for confirmation before fixes).

Frequently Asked Questions about deslop

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

FAQPage Schema
How do I harden AI-generated code for production readiness without changing business logic?

Production hardening for AI-generated code is achieved through a two-phase audit and fix workflow that evaluates error handling, security, and resilience. This process generates a structured AUDIT.md and then applies safety-ordered fixes while preserving intended business logic.

What is the best way to audit a fragile codebase for security and error handling issues?

Auditing a fragile codebase involves reconstructing the codebase map, scanning patterns for consistency, tracing critical paths for resilience, and evaluating OWASP Top 10 style security issues. This produces machine-parseable findings structured in an AUDIT.md file.

How does the two-phase workflow for codebase refactoring safety work?

The two-phase workflow enforces refactoring safety by strictly separating auditing from fixing. Phase 1 generates a structured AUDIT.md, and Phase 2 consumes that file to apply safety-ordered fixes. Phase 2 never starts without explicit user confirmation.

Can I apply fixes automatically during a codebase security audit?

Fixes during a security audit are not applied automatically or immediately. The process enforces a strict two-phase workflow where Phase 2 applies fixes using a safety-tiered protocol, requiring user approval for higher-risk changes and characterization tests for intermediate tiers.

Does this production readiness audit work with any programming language or framework?

The audit is language-agnostic and stack-aware, meaning it reconstructs the codebase map and scans patterns regardless of the specific programming language. It systematically evaluates consistency, resilience, and security hygiene across diverse existing repositories.

What are the limitations of using safety tiers for code hardening fixes?

Safety-tiered code hardening fixes require explicit guardrails that limit automation. Tier 3 changes mandate user approval, and Tier 2 changes require characterization tests, meaning higher-risk refactoring cannot proceed without passing these safety checkpoints.