autonomous-task-auditor
Skill1 starsChanged 41 days agoMITView on GitHub
Autonomous task auditor, implicit requirements deconstructor, and self-healing quality engine.
- Deletes or force-pushes
In this repository11 other files it gives its agents.
- antigravity-guideSkill
- bespoke-frontend-masterSkill
- create-design-mdSkill
- ecommerce-payments-engineSkill
- fullstack-security-auditorSkill
- image-generation-studioSkill
- master-orchestratorSkill
- modern-data-engineerSkill
- resilient-backend-architectSkill
- seo-growth-architectSkill
- superpowers-execution-harnessSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 51
Before finalizing any task, evaluate these diagnostic vectors and fix any gaps immediately:
- Distinctive: line 61
Do error responses leak sensitive database errors, stack traces, or internal server paths?
- Very specific: line 84
Max 3 Healing Iterations (
attempts <= 3): If the build or test continues to fail after 3 consecutive repair attempts, STOP immediately.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
🧠 Autonomous Task Auditor — Dynamic Quality Engine & Self-Healing Loop
This skill completely eliminates AI complacency and premature "done" claims. It dynamically analyzes explicit and implicit requirements from user prompts, investigates global best practices, ruthlessly self-audits generated deliverables, verifies assumptions against physical code on disk (Disk as SSOT), and autonomously resolves defects via Self-Healing before presenting work to the user.
⚡ 1. Core Philosophy: Zero Burden on the User
- No User-Side Debugging: The user must never be forced to hunt for edge cases, missing states, or prompt oversights.
- Generous Reasoning & Research: Leverage deep thinking, documentation lookups, security audits, and automated verification commands (
npm run build,tsc --noEmit). - Disk Verification over Chat Memory: Old conversation snippets or abandoned prototypes must never be assumed to be live code. Every assumption must be verified empirically via
view_fileorgrep_searchagainst the file system.
🔄 2. The 5-Stage Autonomous Loop
[User Prompt / Goal]
│
▼
1. [DYNAMIC INTENT & IMPLICIT REQUIREMENTS ANALYSIS]
• Uncover unspoken yet essential architectural, resilience, and UX requirements.
│
▼
2. [GLOBAL BENCHMARK & DEEP RESEARCH]
• Identify industry-standard patterns, security vulnerabilities, and accessibility baselines.
│
▼
3. [EXHAUSTIVE & PRODUCTION-READY EXECUTION]
• Zero TODOs, zero fake mocks, zero placeholder architecture.
│
▼
4. [RUTHLESS AUDITING & AUTONOMOUS SELF-HEALING]
• "Where will this break? What edge case crashes this? What state is missing?"
• Auto-fix all discovered defects behind the scenes BEFORE presenting to user.
│
▼
5. [EMPIRICAL VERIFICATION & DELIVERABLE AUDIT CARD]
• Validate via `build` / `typecheck` commands (Exit Code 0).🔬 3. Critical Self-Audit Inquiries
Before finalizing any task, evaluate these diagnostic vectors and fix any gaps immediately:
A. Scope & Edge Cases
- Are all logical boundaries and edge cases handled?
- How does the system respond to empty data, massive datasets (100k+ rows), or malformed inputs?
- What is displayed when client/server connectivity drops or an external service times out?
B. Security & Resilience
- Are there any untyped inputs, skipped validations, or loose
anytypes? - Are authentication, authorization (RBAC), and object-level isolation (IDOR protection) strictly enforced?
- Do error responses leak sensitive database errors, stack traces, or internal server paths?
- Are rate limits and quota guards in place to prevent resource exhaustion or token depletion?
C. Design Integrity & User Experience (Anti-AI-Slop)
- Does the interface honor the project's existing design system, or was a generic template pasted?
- Are all semantically applicable states (Default, Loading/Skeleton, Empty, Error, Optimistic) implemented?
- Is horizontal overflow (
overflow-x) completely eliminated across all screen sizes (320px to 4K)?
🚪 4. Autonomous Self-Healing Protocol & Safety Circuit Breakers
[Defect or Edge Case Discovered During Audit]
│
▼
1. Identify root cause and regression risks.
2. Edit target files directly (`replace_file_content` / `write_to_file`) without asking the user.
3. Re-run verification commands (`npm run build`, `npx tsc --noEmit`).
4. Verify progress: error count must decrease with each attempt.🛑 Circuit Breaker & Safe Execution Gates:
- Max 3 Healing Iterations (
attempts <= 3): If the build or test continues to fail after 3 consecutive repair attempts, STOP immediately. Do NOT enter an infinite repair loop. Halt and provide a root-cause summary and terminal logs to the user. - Destructive Command Ban: Autonomous self-healing must NEVER execute destructive git or filesystem commands (
git reset --hard,git clean -fd,rm -rf,DROP TABLE). Uncommitted user modifications must always be protected.
📋 5. Deliverable Audit Card
Conclude completed tasks with a concise audit summary:
### 📋 Autonomous Task Audit Summary
* 🎯 **Dynamic Scope:** Fully satisfied explicit intent and implicit architectural requirements.
* 🛡️ **Security & Resilience:** Strict validation, rate limiting, timeout budgets, and sanitized error masking.
* 🎨 **UI/UX & States:** Conforms to project design tokens and applicable component states.
* 🔧 **Autonomous Fixes:** [List of issues automatically identified and resolved during self-audit].
* ✅ **Empirical Verification:** `npx tsc --noEmit` & `npm run build` (Exit Code 0).Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

