skills.rest
darelabs-tech
darelabs-techOFFICIAL
Explore all skills by this author →
GitHub

dare-review

Audit software task implementations against technical specifications for DARE methodology compliance.

Updated Jul 20, 2026
Search Tags:#quality assurance#code review#task validation#semantic analysis#software audit#dare-method
One-click install
npx skills add https://github.com/darelabs-tech/dare-cli --skill dare-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dare-review
Source: https://github.com/darelabs-tech/dare-cli/tree/main/.agents/skills/dare-review
Command: npx skills add https://github.com/darelabs-tech/dare-cli --skill dare-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the gap between static code analysis and functional correctness by performing a semantic audit of software tasks to ensure they meet the specific criteria defined in the DARE methodology.

Core Features & Use Cases

  • Semantic Validation: Verifies that the implementation satisfies every requirement listed in the task specification, going beyond simple linting.
  • Quality Gatekeeping: Prevents tasks from being marked as DONE if they contain stubs, mocks in production code, or incomplete features.
  • Use Case: Use this skill when a developer submits a task for review to ensure that the code not only compiles but also fulfills the business logic and security requirements promised in the design phase.

Quick Start

Run the dare-review skill to perform a semantic audit of the task with ID task-034 by comparing the implementation against its specification.

Frequently Asked Questions about dare-review

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

FAQPage Schema
How does semantic code review differ from standard linting for task validation?▼

Semantic code review goes beyond standard linting by cross-referencing technical specifications with actual source code to detect logical gaps and verify that implementations fulfill business logic and security requirements.

How do I audit source code against technical specifications to detect incomplete features?▼

You can audit source code by running a semantic verification against defined requirements, which cross-references task specification files with the project codebase to detect logical gaps, stubs, and incomplete features.

Can I use semantic analysis to block tasks with mocks in production code from being marked as done?▼

Yes, semantic quality audit acts as a quality gatekeeper by preventing tasks from being marked as DONE if they contain stubs, mocks in production code, or incomplete features that fail to satisfy specification criteria.

What files do I need to perform a software audit using the dare-method?▼

To perform a software audit using the dare-method, you need access to task specification files and the project codebase to execute semantic verification against the defined criteria-based requirements.

When should I use semantic verification instead of static code analysis for quality assurance?▼

Use semantic verification instead of static code analysis when you need to validate criteria-based completion and ensure the code fulfills the business logic promised in the design phase, closing the gap between static analysis and functional correctness.

Related Skills

Explore More Software Engineering Skills→
nnexainnexai
1

gsd-audit-uat

Audits phase-level project docs and generates prioritized human test plans.

Community
Advanced
xxihxxih
1

quality-verify

Run verification commands and record results in .quality/quality-check.md.

Community
Intermediate
zerielribeirozerielribeiro

lint-and-validate

Run ESLint, Ruff, and MyPy to lint and statically analyze JavaScript and Python code.

Community
Intermediate
Ibrahim-3dIbrahim-3d
371

eval-business-logic

Evaluate business-logic implementations for rule compliance, edge cases, and state transitions.

Community
Advanced