Slop always rolls downhill. Aposlop helps to push back.
Aposlop is a fast command-line tool. It finds duplicate code, excessive file length, and cyclomatic complexity.
Aposlop supports Go, Rust, Python, TypeScript, and TSX. Aposlop uses Tree-sitter to parse each supported language.
Documentation: https://aposlop.ezygang.digital/
Source Code: https://github.com/EzyGang/aposlop
Issues: https://github.com/EzyGang/aposlop/issues
- Why Aposlop?
- Installation
- Quick Start
- Core Features
- Configuration
- CLI Quick Reference
- Contributing
- License
Coding agents can add repeated logic, complex control flow, and large files faster than reviewers can find them. Aposlop gives people and agents one fast check for these problems.
Built for agent-written code. Aposlop finds copies even after names or values change.
Clear limits. Set rules for duplicate code, complexity, and file length.
Useful results. Read source findings in the terminal or use stable JSON in other tools.
Fast feedback. Parallel analysis and a local cache keep repeat checks short.
| Need | Why it matters | How Aposlop helps |
|---|---|---|
| Find copied logic | Renamed values can hide a copy from text search | Tree-sitter finds exact, changed, and near-match copies |
| Keep code clear | Deep control flow is hard to review and change | Language rules measure complexity for each code block |
| Keep files focused | Large files can collect unrelated work | File limits can vary by language and extension |
| Check every change | Slow checks are easy to skip | Native code, parallel work, and caching reduce wait time |
| Support automation | Agents and CI need stable results | JSON output, fixed ordering, and aposlop ci support repeat checks |
Bundled skills help agents use Aposlop and make smaller code and test changes. Install them separately from the CLI.
| Skill | Use it for | How to use it |
|---|---|---|
aposlop |
Install, configure, run, and read Aposlop | Ask the agent to scan or set up a project |
aposlop-code-changes |
Make the smallest complete code change | It starts automatically for code changes |
aposlop-test-changes |
Add a few tests that protect behavior | It starts automatically for test work |
aposlop-deslop-tests |
Remove tests without a distinct purpose | Run /aposlop-deslop-tests [scope] |
aposlop-deslop-turbo |
Reduce tests and production code without behavior changes | Run /aposlop-deslop-turbo [scope] |
Read the agent skills guide for installation and examples.
Aposlop has two components:
- The CLI scans source code and reports findings.
- Agent skills guide coding agents during setup, coding, testing, and cleanup.
Install either component or both.
Install cosign. Then run the installer:
curl -fsSLo install.sh https://github.com/EzyGang/aposlop/releases/latest/download/install.sh
sh install.shInstall cosign. Then run the installer:
Invoke-WebRequest https://github.com/EzyGang/aposlop/releases/latest/download/install.ps1 -OutFile install.ps1
powershell -ExecutionPolicy Bypass -File .\install.ps1Both scripts verify the archive checksum and Sigstore signatures.
Install Aposlop from crates.io:
cargo install aposlop --lockedInstall Aposlop as a global tool:
uv tool install aposlopRun Aposlop without installing it:
uvx aposlop --helpInstall Aposlop from the EzyGang Homebrew tap:
brew install EzyGang/tap/aposlopInstall Aposlop from source. A stable Rust toolchain must support edition 2024.
git clone https://github.com/EzyGang/aposlop.git
cd aposlop
cargo install --path . --lockedVerify the installation:
aposlop --version
aposlop --helpUse the installed CLI:
aposlop install-skillsThe command uses npx when available.
It uses pnpm dlx when npx is unavailable.
You can also run either installer directly:
npx skills@latest add EzyGang/aposlop
pnpm dlx skills@latest add EzyGang/aposlopThe installer lets you choose the skills and target agents. The skills do not install the Aposlop CLI. Read the agent skills guide for each skill.
Aposlop checks for a new GitHub release during interactive runs. It performs a network request at most once every 24 hours. It stores the latest result in the user cache directory. Non-interactive commands do not perform this check.
Set this environment variable to disable the check:
APOSLOP_NO_UPDATE_CHECK=1 aposlop .Analyze the current directory:
aposlop .Show the source for each duplicate:
aposlop . --terminal-output codeRun CI validation:
aposlop ci .The ci command returns exit code 1 when a finding remains.
Write the complete report as JSON:
aposlop . --format json > aposlop-report.jsonRead the full quick-start guide.
A block enters analysis when it meets the line and named-node limits.
Aposlop classifies block relations in this order:
- Type-1 requires identical canonical syntax.
- Type-2 allows different identifiers and literals.
- Type-3 requires a Jaccard similarity at or above the configured threshold.
Aposlop reports each connected set of duplicate relations as one group. Two blocks do not match when either contains the other in the same file. A TypeScript block can match a TSX block.
Each valid block has an initial complexity score of 1.
Aposlop adds one for each language-specific decision.
Decisions include branches, loops, alternatives, exception paths, conditional expressions, and short-circuit operations.
A nested block has an independent score. Nested blocks include functions, closures, lambdas, field initializers, and static blocks.
A violation requires:
score > complexity_threshold
Aposlop reports a supported source file when its line count exceeds its effective maximum.
The default maximum is 300 lines.
lines > max_file_lines
Use [file_length].exclude for check-specific gitignore-style exclusions.
File-length violations cannot be suppressed with aposlop allow.
| Language | Extensions |
|---|---|
| Go | .go |
| Rust | .rs |
| Python | .py |
| TypeScript | .ts |
| TSX | .tsx |
Aposlop ignores unsupported extensions.
Aposlop follows standard ignore files such as .gitignore.
The terminal report is the default. It contains duplicate groups, complexity findings, file-length violations, diagnostics, and a summary.
aposlop . --format terminalThe JSON report contains the complete report and its schema version.
aposlop . --format jsonThe ci command shows only the status and finding counts.
aposlop ci .Aposlop assigns a deterministic five-character ID to each duplicate group or complexity finding.
Add a finding to the manual exclusions:
aposlop allow aB7_xThe command writes the ID to .aposlopignore.
Delete the ID from that file to restore the finding.
Aposlop reports valid IDs that match no current finding as unused ignores at the end of each report.
Unused ignores do not change the process exit code.
File-length violations have no finding ID and cannot be added to .aposlopignore.
Aposlop reads <PATH>/.aposlop.toml.
Aposlop uses built-in values when this file does not exist.
[core]
min_lines = 5
min_nodes = 30
exclude = ["tests/", "vendor/", "node_modules/", "target/"]
use_cache = true
[duplicates_detection]
type_1 = true
type_2 = true
type_3 = true
type_3_threshold = 0.85
[metrics]
calculate_complexity = true
complexity_threshold = 15
[file_length]
max_lines = 300
exclude = []core.exclude and file_length.exclude use the same syntax as one .gitignore line.
core.exclude removes matching paths from all analysis.
file_length.exclude suppresses only file-length violations.
Directory patterns match at any depth, while / anchors and ** recurse.
Language and extension tables can override max_file_lines and the existing analysis rules.
Command-line values override all configuration-file layers.
Read the complete CLI reference.
Open a GitHub issue to discuss a large change. Then open a pull request.
Run these checks before you submit the pull request:
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features
cargo run -- --helpYou can use Aposlop under either license: