dk-slop-audit

Scan codebases for misplaced files, dead code, temp files, and security/config slop; generate prioritized P0-P4 reports with guidance for P0-P2 items.

87|12|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/deepklarity/harness-kit --skill dk-slop-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dk-slop-audit
Source: https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/dk-slop-audit
Command: npx skills add https://github.com/deepklarity/harness-kit --skill dk-slop-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slop accumulates in codebases, leading to wasted developer time, hidden defects, and brittle releases. This audit identifies misplaced files, dead code, temporary artifacts, security/config slop, structural anomalies, and dependency drift, surfacing a prioritized cleanup report.

Core Features & Use Cases

  • Automated discovery of misplaced files, dead code, and temporary artifacts.
  • Security and configuration slop scanning to surface exposures and misconfigurations.
  • Prioritized, action-oriented report with P0-P4 findings and remediation guidance.
  • Use Case: run before releases or major refactors to clean the repository and reduce risk.

Quick Start

Run the hygiene audit across the repository or a targeted scope to generate a prioritized slop report.

Frequently Asked Questions about dk-slop-audit

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

FAQPage Schema
How do I audit my codebase for dead code and misplaced files before a release?

A codebase hygiene audit scans your repository to identify misplaced files, dead code, temporary artifacts, and security misconfigurations. It categorizes findings into P0-P4 priorities, generating an action-oriented report to reduce release risk and technical debt.

Can I run a codebase slop scan on a specific directory instead of the entire repository?

Yes, you can apply the audit across the entire project or targeted scopes such as specific directories, branches, or teams. This generates a prioritized slop report with detailed P0-P2 remediation guidance focused on your selected area.

What is codebase slop and how does it affect software quality?

Codebase slop is the accumulation of misplaced files, dead code, temporary artifacts, and security or configuration drift. It leads to wasted developer time, hidden defects, and brittle releases, making automated detection and cleanup essential for maintaining software quality.

What's the best way to identify security and configuration slop in my repository?

The best way to identify security and configuration slop is to run an automated scan that surfaces exposures and misconfigurations. This produces a prioritized report with P0-P4 findings and detailed remediation guidance to quickly address security risks.

Does the automated slop report include guidance on how to fix the identified issues?

Yes, the automated audit generates an action-oriented report that categorizes findings into P0-P4 priorities and produces detailed P0-P2 remediation guidance. This helps developers quickly resolve critical misplaced files, dead code, and security slop.