mine.challenge

Critique code designs using three adversarial reviewer personas.

1|Updated Feb 22, 2026

Search Tags:#quality assurance #code review #refactoring #software architecture #adversarial testing #design critique

Ready to run

npx skills add https://github.com/NodeJSmith/Claudefiles --skill mine-challenge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mine.challenge
Source: https://github.com/NodeJSmith/Claudefiles/tree/main/skills/mine.challenge
Command: npx skills add https://github.com/NodeJSmith/Claudefiles --skill mine-challenge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill rigorously critiques code designs by assuming they are flawed, identifying specific weaknesses, and proposing concrete improvements.

Core Features & Use Cases

Adversarial Critique: Employs three distinct personas (Senior Engineer, Architect, Adversarial Reviewer) to find design flaws from multiple angles.
Evidence-Based Findings: Requires all claims to be backed by specific code citations or external references.
Actionable Recommendations: Provides clear "better approach" suggestions and design questions for each identified issue.
Use Case: Before committing to a new feature's implementation, use this Skill to ensure the underlying design is robust, maintainable, and free from critical flaws.

Quick Start

Use the mine.challenge skill to critique the design of the 'auth module'.

Frequently Asked Questions about mine.challenge

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

FAQPage Schema

How do I perform an adversarial code review to find design flaws?▼

Adversarial code review identifies fundamental design flaws by simulating three distinct reviewer personas—a Senior Engineer, an Architect, and an Adversarial Reviewer—to analyze static code and cite evidence for all claims.

What is the best way to critique software architecture before implementing a new feature?▼

Critiquing software architecture before implementation involves assuming the design is flawed, rigorously identifying specific weaknesses through multi-persona static analysis, and proposing actionable refactoring approaches and design questions.

Do I need to execute my code to get an architectural design critique?▼

No, architectural design critique requires no external execution, focusing entirely on static code analysis and conceptual review to identify maintainability issues and fundamental flaws without running the application.

How does evidence-based code review improve software architecture?▼

Evidence-based code review improves software architecture by requiring all identified design flaws to be backed by specific code citations or external references, ensuring actionable recommendations are grounded in the actual implementation.

What are the limitations of static design critique for refactoring?▼

Static design critique limitations include an inability to detect runtime execution flaws or performance bottlenecks, as it relies solely on conceptual review and source analysis without external execution or dynamic adversarial testing.