slop-score

Measure code slop across six axes and enforce worst-first remediation.

30|12|Updated Jun 21, 2026

Search Tags:#automation #testing #refactoring #go #code-quality #technical-debt

Ready to run

npx skills add https://github.com/anthony-chaudhary/fak --skill slop-score

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slop-score
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/slop-score
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill slop-score

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the accumulation of non-compiler-detectable code rot—such as copy-paste clones, vacuous tests, and dead symbols—that degrades software quality over time.

Core Features & Use Cases

Code Slop Measurement: Runs a deterministic scorecard across six axes (HARD and SOFT) to generate a slop-debt metric.
Worst-First Remediation: Provides a structured workflow to retire debt by prioritizing the most impactful fixes, such as extracting shared helpers or adding meaningful test assertions.
Verification & Audit: Ensures all fixes are genuine and verified through build, test, and commit-audit gates, preventing the gaming of metrics.

Quick Start

Run the slop-score skill to measure the current code debt and identify the highest priority items for remediation.

Frequently Asked Questions about slop-score

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

FAQPage Schema

How do I measure technical debt in a Go codebase?▼

To measure technical debt in a Go codebase, run a deterministic scorecard across six axes to generate a slop-debt metric. This identifies non-compiler-detectable code rot like copy-paste clones, vacuous tests, and dead symbols.

What is the best way to prioritize code refactoring for hidden technical debt?▼

The best way to prioritize code refactoring is to use a worst-first remediation loop. This workflow structures the retirement of technical debt by prioritizing the highest impact fixes, such as extracting shared helpers or adding meaningful test assertions.

Do I need Python to measure code quality and technical debt in Go repositories?▼

Yes, you need Python installed to execute the deterministic scorecard that measures code quality and technical debt in Go repositories. The scorecard runs via Python to evaluate the codebase against six quality axes.

How does the commit-audit protocol verify code refactoring changes?▼

The commit-audit protocol verifies code refactoring changes by enforcing build, test, and commit-audit gates. This ensures all fixes are genuine and verified, preventing developers from gaming the technical debt metrics.

What types of code rot does a code slop scorecard detect?▼

A code slop scorecard detects non-compiler-detectable code rot that degrades software quality over time. It specifically targets issues like copy-paste clones, vacuous tests, and dead symbols that standard compilers ignore.

How do I eliminate vacuous tests and copy-paste clones in my Go project?▼

To eliminate vacuous tests and copy-paste clones in a Go project, apply a worst-first remediation workflow after measuring the slop-debt metric. This structured loop enforces genuine fixes verified through build, test, and commit-audit gates.