anneal

Detect and repair AI-introduced code slop over a specified duration.

3.2k|219|Updated Jul 27, 2024
One-click install
npx skills add https://github.com/av/harbor --skill anneal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anneal
Source: https://github.com/av/harbor/tree/main/.agents/skills/anneal
Command: npx skills add https://github.com/av/harbor --skill anneal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The anneal Skill unit addresses the issue of AI-introduced architectural decay in codebases, such as duplicated logic, over-engineering, and silent error swallowing, by systematically fixing these issues over a user-defined duration.

Core Features & Use Cases

  • Code Slop Detection and Repair: Identifies and fixes AI-introduced code slop patterns like duplication, over-engineering, and silent error swallowing.
  • User-Defined Duration: Allows users to specify how long the codebase should be analyzed and fixed.
  • Safety Protocol: Follows a strict safety protocol that includes running tests, making one focused change at a time, and reverting on failure.

Quick Start

Run the 'anneal' skill on your codebase for 4 hours to systematically fix AI-introduced code slop.

Frequently Asked Questions about anneal

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

FAQPage Schema
How do I fix AI-introduced code slop in my codebase?

To fix AI-introduced code slop, you can run a systematic process that detects and repairs architectural decay like duplicated logic and over-engineering over a user-specified duration. The process uses subagents to perform individual fixes, run tests, and commit changes.

What is AI code slop and how does it affect code maintenance?

AI code slop is architectural decay introduced by AI, including duplicated logic, over-engineering, and silent error swallowing. It degrades code maintenance by creating hidden technical debt that accumulates silently during automated generation.

How do I safely remove over-engineered code without breaking APIs?

You can safely remove over-engineered code by following a strict safety protocol that makes one focused change at a time, runs tests, and reverts on failure. This ensures no changes occur to public APIs or external behavior.

Can I automate silent error swallowing detection and repair?

Yes, you can automate silent error swallowing detection and repair by running a systematic analysis over a defined duration. Subagents identify these specific code slop patterns, apply fixes, run tests, and commit the changes automatically.

What's the best way to run systematic code optimization over several hours?

The best way to run systematic code optimization over several hours is to specify a user-defined duration for the process. Subagents will continuously detect and repair code slop patterns, verifying every change with tests before committing.

Are there limitations when automatically fixing architectural decay?

A key limitation when fixing architectural decay is that the process is bound by your specified duration and strict safety protocols. It makes one focused change at a time and reverts on test failure, ensuring no public API or external behavior is altered.