asshole

Review all errors in the latest commit and require acknowledgment.

15|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/spences10/skills --skill asshole-spences10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asshole
Source: https://github.com/spences10/skills/tree/main/asshole
Command: npx skills add https://github.com/spences10/skills --skill asshole-spences10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a thorough and accurate record of all errors and failures, promoting a culture of accountability and thoroughness in software development.

Core Features & Use Cases

  • Comprehensive Error Reporting: Forces acknowledgment of all failures, including those unrelated to the current task.
  • Preventive Reporting: Encourages the user to investigate and address all reported issues.
  • Use Case: When reviewing a pull request, this Skill ensures that all issues, including those pre-existing, are discussed and addressed.

Quick Start

Run the 'asshole' skill to review all errors in the latest commit.

Frequently Asked Questions about asshole

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

FAQPage Schema
How do I ensure all build failures are acknowledged during code review?▼

To ensure all build failures are acknowledged during code review, you need a process that forces comprehensive error reporting and prevents failure dismissal. This approach requires proper acknowledgment of all errors and encourages investigation into root causes to enhance software quality and accountability.

What is comprehensive error reporting in software development?▼

Comprehensive error reporting in software development is the practice of maintaining a thorough and accurate record of all test results and build output failures. It prevents failure dismissal by ensuring that all issues, including pre-existing ones, are discussed and addressed.

How do I track pre-existing issues when reviewing a pull request?▼

To track pre-existing issues when reviewing a pull request, you implement a thorough reporting mechanism that surfaces all errors, including those unrelated to the current task. This ensures all reported issues are discussed and addressed rather than dismissed.

Can I use this failure tracking approach for unrelated build errors?▼

Yes, this failure tracking approach is specifically designed to force acknowledgment of all failures, including those unrelated to the current task. It encourages users to investigate and address all reported issues to maintain thoroughness in software development.