dcyfr-validation

Automate pre-completion validation checklists and approval gates for OpenCode workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dcyfr/dcyfr-labs --skill dcyfr-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcyfr-validation
Source: https://github.com/dcyfr/dcyfr-labs/tree/main/.opencode/skill/dcyfr-validation
Command: npx skills add https://github.com/dcyfr/dcyfr-labs --skill dcyfr-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates code readiness by enforcing pre-completion checklists and gating approvals to prevent unreviewed changes from merging.

Core Features & Use Cases

  • Pre-completion checklist validation: TypeScript compile, lint, tests, and design-token compliance to catch issues before finalization.
  • Approval gates for breaking changes and architecture decisions to avoid risky deployments.
  • Escalation and manual review triggers to route high-risk changes to the right stakeholders.
  • Common failure pattern guidance to help teams diagnose and fix issues quickly.

Quick Start

Provide the project changes and run the validation workflow to ensure all gates pass before merging.

Frequently Asked Questions about dcyfr-validation

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

FAQPage Schema
How do I enforce pre-release quality gates for TypeScript and linting before merging?

Pre-release quality gates are enforced by automating validation checklists that run TypeScript compile checks, linting, and tests during pull request finalization to prevent unreviewed changes from merging.

What is an approval gate in CI and when do I need it for breaking changes?

An approval gate in CI is an automated checkpoint that blocks risky modifications from deploying. You need it for breaking changes and architecture decisions to ensure stakeholders review high-risk code before merging.

How do I set up pre-completion validation checklists for pull request reviews?

Pre-completion validation checklists are set up by applying automated workflow rules during PR finalization, triggering checks for TypeScript compilation, linting, tests, and design-token compliance before a merge is authorized.

Can I trigger manual escalation for high-risk changes during CI validation?

Manual escalation for high-risk changes is supported during CI validation. The workflow includes escalation and manual review triggers designed to route architecture decisions and breaking changes to the appropriate stakeholders.

Why does design-token compliance fail during pre-completion checklist validation?

Design-token compliance fails during pre-completion checklist validation when updated code does not adhere to established UI token standards. The workflow provides common failure pattern guidance to help diagnose and resolve these issues quickly.