autocorrect

Capture and review code and documentation corrections via git hooks and monthly reviews.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/bllshttng/footnote --skill autocorrect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autocorrect
Source: https://github.com/bllshttng/footnote/tree/main/skills/autocorrect
Command: npx skills add https://github.com/bllshttng/footnote --skill autocorrect

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the review and correction of code and documentation mistakes, reducing manual errors and improving code quality.

Core Features & Use Cases

  • Passive Capture: Captures corrections passively through git hooks, verifiers, and insights tags.
  • Monthly Review: Provides a monthly review via a fresh Claude API call against the current rule text.
  • Interactive Triage: Allows users to triage proposed patches interactively.
  • Use Case: Use when the user wants to review corrections, run an autocorrect review, triage proposed patches, install the autocorrect schedule, ingest insights, check autocorrect status, or audit recurring mistake classes in the toolkit.

Quick Start

Run the autocorrect skill to start the monthly review process.

Frequently Asked Questions about autocorrect

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

FAQPage Schema
How do I automate code review and error correction for documentation mistakes?

Automating code review for documentation mistakes involves capturing corrections passively through git hooks and verifiers, then using AI-driven monthly reviews to validate rule text. You can interactively triage proposed patches to verify ongoing code and documentation quality.

What is passive capture for code corrections and how does it work?

Passive capture for code corrections works by automatically recording mistakes through git hooks, verifiers, and insights tags. This mechanism continuously gathers error correction data without manual input, feeding it into an AI-driven review process.

How do I run an automated monthly review for recurring code mistakes?

Running an automated monthly review executes a fresh API call against your current rule text to evaluate captured corrections. This process audits recurring mistake classes in your toolkit, allowing you to interactively triage proposed patches.

Can I use git hooks to capture error corrections passively?

Yes, you can use git hooks to capture error corrections passively. The system uses git hooks alongside verifiers and insights tags to automatically document corrections, creating an ongoing record for monthly AI-driven review and interactive patch triage.

How do I triage proposed patches for code quality improvements?

Triaging proposed patches for code quality improvements is handled through an interactive user interface after the monthly review. This allows you to verify ongoing improvement by validating AI-driven corrections against your current code and documentation rules.