are-you-sure

Automate fresh-eyes self-review and repair of code, config, tests, and docs.

17|Updated May 24, 2014
One-click install
npx skills add https://github.com/blacktop/dotfiles --skill are-you-sure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: are-you-sure
Source: https://github.com/blacktop/dotfiles/tree/main/ai/skills/are-you-sure
Command: npx skills add https://github.com/blacktop/dotfiles --skill are-you-sure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a crucial self-review step to catch obvious bugs, regressions, and risky assumptions before finalizing code, configuration, tests, or documentation.

Core Features & Use Cases

  • Automated Code Review: Performs a quick, deliberate second pass on recent changes.
  • Issue Identification & Fixing: Detects and attempts to fix clear, local issues in code, config, tests, or docs.
  • Use Case: After an agent modifies a Python script, it can use this skill to review the changes for common errors, ensure tests still pass, and fix any simple mistakes before presenting the updated code.

Quick Start

Use the are-you-sure skill to review the changes you just made with fresh eyes.

Frequently Asked Questions about are-you-sure

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

FAQPage Schema
How do I automate a fresh-eyes code review for recent changes?

Code review automation works by performing a quick, deliberate second pass on recent changes to detect and fix clear, local issues in code, configuration, tests, or documentation.

How do I catch regressions and risky assumptions before finalizing code?

Catch regressions and risky assumptions by applying a structured workflow for scope reconstruction and risk assessment across five buckets to verify changes before finalization.

Can I use this self-review process for configuration and documentation, not just code?

Yes, the self-review and repair process supports identifying and fixing clear, local issues in code, configuration, tests, and documentation changes.

What is the best way for an agent workflow to self-review its modifications?

Agent workflows can self-review modifications by triggering an automated second pass that assesses risk across five buckets and attempts to fix simple mistakes before presenting changes.

Does this self-review skill require external testing dependencies to work?

No, the self-review skill has no external dependencies and operates independently to perform targeted verification and issue fixing on recent modifications.

When should I avoid using an automated self-review for debugging?

Automated self-review should be avoided for complex, non-local debugging issues, as it specifically targets clear, local issues and obvious bugs rather than deep architectural flaws.