my-validate

Verify project work against a plan or session context and flag discrepancies.

4|1|Updated May 31, 2015
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill my-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: my-validate
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-validate
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically verify work against a project plan or the current session context, and attempt corrective actions before escalation.

Core Features & Use Cases

  • Dual-mode validation: Plan Mode and Session Mode, enabling verification against either a plan file or live context.
  • Automated self-repair: Attempts to fix verifiable issues in place and reports unresolved items for human review.
  • Observability integration: Optionally validates instrumentation if a companion observability plan exists, augmenting reports with traces and metrics.
  • Output: Generates a concise validation report detailing verification results, repairs performed, and recommendations.

Quick Start

Run my-validate to verify the current session and any plan context, with automated self-repair on failures.

Frequently Asked Questions about my-validate

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

FAQPage Schema
How do I verify code changes against a project plan?▼

Verifying code changes against a project plan involves cross-referencing current work with plan context. This skill identifies claims, flags discrepancies, and ensures output reflects actual code state.

Can code validation automatically repair discrepancies it finds?▼

Automated self-repair can fix verifiable issues in place during validation. It escalates only unresolved issues for human review and generates a concise report with repairs and recommendations.

How does observability integration work during session validation?▼

Observability integration validates instrumentation when a companion plan exists, augmenting the validation report with traces and metrics to verify the actual code state.

What is the difference between plan mode and session mode for verifying work?▼

Plan mode verifies work against a plan file, whereas session mode validates against live context. Both modes identify discrepancies and attempt self-repair before escalating.

Do I need a companion observability plan to validate my code?▼

A companion observability plan is optional. Standard validation works with a plan or session context, adding observability traces and metrics only when a companion plan exists.

What does a validation report include after verifying project work?▼

A validation report includes verification results, repairs performed, and recommendations. It concisely details confirmed claims, applied self-repairs, and escalated discrepancies.