skills.rest
JCE-Joshhh77
JCE-Joshhh77COMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-discipline

Plan evidence-first verification with audit trails for code changes.

16|Updated Apr 30, 2026
Search Tags:#testing#debugging#verification#audit#quality#evidence
One-click install
npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill verification-discipline-jce-joshhh77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-discipline
Source: https://github.com/JCE-Joshhh77/JCE-Opencode-Tools/tree/main/config/skills/verification-discipline
Command: npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill verification-discipline-jce-joshhh77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams plan verification tasks with an evidence-first approach, ensuring verifiable outcomes across changes, debugging, implementation, and release workflows.

Core Features & Use Cases

  • Evidence-driven failure analysis and root-cause identification
  • Structured failure loop with iterative fixes and verification
  • Audit-ready documentation and provenance for code changes
  • Adaptable to various languages and project types, with guidance for review and deployment

Quick Start

Provide a focused verification plan for the current change and run the smallest, most relevant tests to confirm correctness.

Frequently Asked Questions about verification-discipline

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

FAQPage Schema
How do I create an audit trail for code changes during debugging?▼

An audit trail for code changes is generated through evidence-first verification planning, documenting root-cause analysis and iterative fixes with clear provenance for each step.

What is an evidence-first verification plan for software testing?▼

Evidence-first verification planning structures testing tasks to ensure verifiable outcomes, applying controlled test selection and structured failure loops across debugging, implementation, and release workflows.

How do I structure a failure loop for iterative debugging fixes?▼

A structured failure loop for debugging applies evidence-driven failure analysis to identify root causes, guiding iterative fixes and running the smallest, most relevant tests to confirm correctness.

Can I use this verification approach across multiple programming languages and project types?▼

Yes, the evidence-first verification and audit planning approach is adaptable to various languages and project types, providing guidance for code review and deployment workflows without language-specific constraints.

How do I run the smallest relevant tests to confirm a code change?▼

You confirm a code change by providing a focused verification plan that selects and runs only the smallest, most relevant tests, ensuring verifiable outcomes through controlled test selection.

What is the best way to document provenance for software release verification?▼

The best way to document provenance for releases is applying evidence-first verification planning, which creates audit-ready documentation tracking root-cause analysis and structured failure resolution across changes.

Related Skills

Explore More Software Engineering Skills→
sswapnil2sswapnil2

verification-before-completion

Run verification commands and evaluate outputs before claiming completion.

Community
Advanced
conn-castleconn-castle
9

resolve-findings

Verify audit findings and document which issues require fixes.

Official
Advanced
juliuss1907juliuss1907

systematic-debugging

Automate root cause analysis and systematic debugging across four investigation phases.

Community
Advanced
Handy369Handy369

skills-maker

Create, refactor, or audit skill fixtures using runtime handoff evidence.

Community
Basic