Menu

Individual skill

correct

Find mistake classes agents keep repeating in this repository and block each with the strongest mechanism available (structure, then types and lint, then tests, docs last). Use for "/correct", "agents keep making the same mistake here", or after a repeated correction.

plugins/requie/endostack/skills/correct/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# correct

Find the mistakes agents make over and over in this repository, the ones the user keeps fixing by hand, and change the repository so each one becomes impossible or fails a check automatically. A rule written in prose can be ignored without anything failing. A type, a lint rule, or a deleted code path cannot.

A class of mistake needs at least two occurrences. A one-time slip is not a class.

## The contributor you are designing for

Plan for a future contributor that is an agent: it sees only the files it happens to open, imitates whatever example sits closest, and picks the least effort route that compiles. Your target is a codebase where an edit that looks right from inside one file is right everywhere.

## Steps

### 1. Collect evidence