synthesis-implementation-integrity

Verify non-trivial code changes with seven adversarial integrity passes.

15|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/rajivpant/synthesis-skills --skill synthesis-implementation-integrity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthesis-implementation-integrity
Source: https://github.com/rajivpant/synthesis-skills/tree/main/synthesis-implementation-integrity
Command: npx skills add https://github.com/rajivpant/synthesis-skills --skill synthesis-implementation-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-trivial code changes can appear complete after passing tests, but hidden gaps still threaten production. This skill provides an adversarial self-review protocol to verify that a change is genuinely complete and ready for production.

Core Features & Use Cases

  • Seven integrity passes to systematically verify data flow, boundary adherence, and parity between test and production environments.
  • Guidance to surface placeholders, TODOs, and deferred work that could block shipping.
  • Companion-change awareness ensuring related files, migrations, docs, and configs are updated in tandem.

Quick Start

Run the seven-integrity passes on your latest non-trivial change to confirm everything is complete.

Frequently Asked Questions about synthesis-implementation-integrity

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

FAQPage Schema
How do I verify code completeness before shipping non-trivial changes?

A structured seven-pass integrity review verifies code completeness by systematically auditing data flow chains, detecting placeholders, checking test honesty, ensuring environment parity, and validating companion changes across deployment boundaries.

What is adversarial code review and when do I need it for software verification?

Adversarial code review is a self-assessment technique that aggressively probes non-trivial code changes for hidden gaps. You need it when passing tests alone is insufficient to guarantee production deployment readiness.

How do I catch placeholders, TODOs, and deferred work blocking my deployment?

To catch placeholders and TODOs blocking deployment, apply an adversarial self-review pass that surfaces deferred work through explicit documentation. This ensures incomplete chain elements are verified before shipping.

Does this code audit process check for environment parity between test and production?

Yes, the code audit process includes dedicated integrity passes to verify parity between test and production environments. It checks boundary adherence and environment consistency to prevent production-specific failures.

What is the best way to ensure companion files, migrations, and configs are updated together?

The best way to ensure companion changes is using a review protocol with companion-change awareness, verifying that related files, database migrations, documentation, and configurations are updated in tandem with primary code changes.

Why do my code changes pass tests but still have hidden gaps threatening production?

Code changes pass tests but threaten production when boundary verification, chain completeness, or environment parity are insufficient. An adversarial self-review exposes these hidden gaps through a structured seven-pass verification process.