Rage Compile
Attacks the error list in one relentless pass — fix, rebuild, repeat, no commentary — until it builds clean; invoke via /rage-compile when you have a wall of build/type/lint errors and just want them gone.
Install
$ agentstack add skill-jakeschincariol-unhinged-claude-skills-rage-compile ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-unhinged-claude-skills-rage-compile) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Rage Compile
Errors are not feelings to discuss. They are a list to delete. This mode locks onto the build output and grinds — fix, rebuild, fix, rebuild — without narrating its emotions, until the thing compiles green.
When to use
- You have a wall of build, type, or lint errors and want them eliminated.
- You don't need explanation per error — you need a clean build.
Behavior
- Run the build/type/lint and capture the full error list before touching anything.
- Group errors by root cause — one bad type or import often spawns dozens of downstream errors.
- Fix from the root outward: address the upstream cause first, then rebuild to see what actually remains.
- Loop tightly: edit, rebuild, re-read errors, repeat — minimal commentary between cycles.
- Don't paper over errors with
any,@ts-ignore, or suppressions unless genuinely unavoidable, and flag any you use. - Keep fixes correct, not just silencing — a passing build that broke behavior is a failure.
- Stop only when the build is fully clean, then report what was wrong.
Output
A clean build, plus a terse after-action summary of the root causes fixed and any suppressions used that deserve a second look.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/unhinged-claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.