are-you-sure
Deliberate fresh-eyes self-review and repair after making changes. Use when an agent has just written or modified code, config, tests, or docs and should pause to look for obvious bugs, regressions, missing tests, confusing behavior, or risky assumptions, fix the clear local issues it finds, and only then finalize, hand off, or commit. Supports Claude Code, Codex, and Gemini with provider notes in references/.
Best use case
are-you-sure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deliberate fresh-eyes self-review and repair after making changes. Use when an agent has just written or modified code, config, tests, or docs and should pause to look for obvious bugs, regressions, missing tests, confusing behavior, or risky assumptions, fix the clear local issues it finds, and only then finalize, hand off, or commit. Supports Claude Code, Codex, and Gemini with provider notes in references/.
Teams using are-you-sure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/are-you-sure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How are-you-sure Compares
| Feature / Agent | are-you-sure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deliberate fresh-eyes self-review and repair after making changes. Use when an agent has just written or modified code, config, tests, or docs and should pause to look for obvious bugs, regressions, missing tests, confusing behavior, or risky assumptions, fix the clear local issues it finds, and only then finalize, hand off, or commit. Supports Claude Code, Codex, and Gemini with provider notes in references/.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Are You Sure Do one careful second pass on the changes you just made, and fix the clear issues you find before you declare the work done. ## Read the right reference - Read [references/workflow.md](references/workflow.md) for the provider-neutral fresh-eyes review loop. - Read [references/claude.md](references/claude.md) if this should run in Claude Code. - Read [references/codex.md](references/codex.md) if this should run in Codex. - Read [references/gemini.md](references/gemini.md) if this should run in Gemini CLI. ## Use this skill when - you just edited files and are about to send a final answer - you are about to commit or open a PR - the change involved generated or agent-written code - the edit touched behavior, configuration, tests, or interfaces - you want a quick self-check before asking for a second opinion ## Do not use this skill as - a substitute for real verification - a substitute for a dedicated security audit - a substitute for an external second-opinion review If the change is high-risk, run this skill first, then use a separate review skill. ## Fresh-eyes workflow 1. Reconstruct the exact scope of what changed. 2. Re-read the diff and changed files slowly. 3. Check the five risk buckets from the workflow reference. 4. Run the cheapest meaningful verification you can. 5. If you find a likely issue, inspect neighboring code before concluding. 6. Default to fix mode: if the issue is clear, local, and easy to verify, patch it immediately. 7. Re-run the narrowest relevant verification and repeat the review once. 8. If the fix would widen scope, change architecture, or needs human judgment, stop and report it instead of guessing. 9. Return what you fixed, what still looks risky, or say explicitly that no substantive issues were found. ## Output contract Return in this order: 1. Issues found and fixed, with file references. 2. Issues still remaining or explicitly review-only findings. 3. Verification performed. 4. Residual risk, open questions, or `No substantive issues found`. Keep the review concrete. Do not pad it with praise or a changelog.
Related Skills
second-opinion
Run an external LLM code review with Codex CLI, Gemini CLI, or both. Use when the user asks for a second opinion, external review, Codex review, Gemini review, or wants a model-vs-model review of current changes, a branch diff, a specific commit, or a GitHub pull request.
seatbelt-sandboxer
Generates minimal macOS Seatbelt sandbox configurations. Use when sandboxing, isolating, or restricting macOS applications with allowlist-based profiles.
screenshot-analyzer
Find and analyze screenshots from ~/Downloads/Screenshots/ for UI/UX review. Use when asked to look at screenshots, review UI designs, inspect interface errors, analyze layout issues, or examine visual problems. Triggers on "check my latest screenshot", "review my UI", "analyze this screen capture".
save-session
Save AI agent session information for later resumption. Use when: (1) Finishing a work session and want to save progress (2) User says "save session", "remember this session", or "save your session ID" (3) Before ending a long coding/debugging session (4) When user wants to be able to resume this conversation later Supports Claude, Codex, Gemini, Copilot, Cursor, and other AI agents.
rust-profiling
Profile Rust code using samply to identify CPU bottlenecks. Use when performance is slow, before optimizing, or when the user asks to profile.
ratatui-tui
Build terminal UIs with ratatui following 2026 Rust best practices. Use when: (1) Creating new TUI apps, (2) Adding widgets/layouts, (3) Keyboard navigation/state management, (4) Image integration via ratatui-image, (5) Async event handling, (6) Release optimization. Covers v0.30.0+ API, Elm Architecture, StatefulWidget, color-eyre.
orchestrate
Orchestrate multi-step work with Claude Code CLI as a bounded worker while Codex stays lead developer. Use when Codex should split a task into scoped sub-tasks, delegate planning or implementation to Claude with `claude -p`, run parallel Claude sessions, isolate risky edits in worktrees, define custom Claude subagents, or move repeated enforcement into Claude hooks/settings.
karpathy-guidelines
Behavioral checklist for disciplined LLM coding. Use when starting non-trivial tasks to enforce assumption surfacing, minimal changes, and verifiable goals. Derived from Andrej Karpathy's observations on LLM coding pitfalls.
instruments-profiling
Use when profiling native macOS or iOS apps with Instruments/xctrace. Covers correct binary selection, CLI arguments, exports, and common gotchas.
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. 30c5c8d (Update humanizer plugin to upstream v2.2.0)
html-artifacts
Produce a single self-contained .html artifact (no build, no external assets) when the task is spatial, interactive, visual, multi-axis, or long-running. Triggers on "build me an HTML for X", "make a dashboard / status snapshot / comparison / decision tree / timeline / architecture map", "render this plan as a clickable site", or when content can't fit markdown structurally. Skips short replies, code-only outputs, simple plans.
handoff
Generate optimized handoff prompts for delegating work to another LLM agent. Use when handing work to GPT-5.x/Codex, Claude 4.x, Gemini 3.x, or Grok 4.x, either as a shared-workspace sub-task handoff or a fresh-context handoff for a new session or model. Triggers on requests like "create a handoff prompt", "delegate this task to another agent", "hand this off", or "prepare context for another agent".