skills.rest
nishantnaagnihotri
nishantnaagnihotriCOMMUNITY
Explore all skills by this author →
GitHub

build-evidence-and-merge-readiness

Validate Gate 5/5.5/6 evidence and PR provenance for compliant merges.

Updated Jan 30, 2019
Search Tags:#testing#merge#evidence#bdd#gate-5#pr-provenance#gate-6
One-click install
npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill build-evidence-and-merge-readiness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-evidence-and-merge-readiness
Source: https://github.com/nishantnaagnihotri/tark-vitark/tree/main/.github/skills/build-evidence-and-merge-readiness
Command: npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill build-evidence-and-merge-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams ensure that merge decisions are supported by verifiable evidence, mapping tests to requirements and capturing provenance to prevent unreviewed or unsafe merges.

Core Features & Use Cases

  • Enforces test-first BDD and domain-language usage in PRs.
  • Requires scenario-to-test mapping and a complete PR evidence package.
  • Verifies presence of a full Agent Provenance block and accessibility of merge criteria across Gate 5, Gate 5.5, and Gate 6.

Quick Start

Prepare a PR by including the Agent Provenance block and attach complete Gate 5/5.5/6 evidence according to this skill's protocol.

Frequently Asked Questions about build-evidence-and-merge-readiness

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

FAQPage Schema
How do I automate PR provenance and evidence validation for merge readiness?▼

Automate merge readiness validation by enforcing scenario-to-test mappings, passing tests, rollback notes, and complete PR provenance blocks across Gate 5, 5.5, and 6 to ensure compliant merges.

What is a scenario-to-test mapping in BDD pull requests?▼

Scenario-to-test mapping in BDD PRs links domain-language behaviors to passing test cases, ensuring code changes are traceable to requirements before a merge is approved.

How do I prepare a PR to pass Gate 5, 5.5, and 6 merge checks?▼

Prepare a PR for Gate 5, 5.5, and 6 by including an Agent Provenance block, complete scenario-to-test mappings, passing tests, architecture delta records, and rollback notes.

Why does my pull request fail merge readiness evidence checks?▼

PRs fail merge readiness evidence checks when they omit required provenance blocks, lack scenario-to-test mappings, miss architecture delta records, or have incomplete rollback notes.

Do I need rollback notes and architecture delta records for a compliant merge?▼

Yes, rollback notes and architecture delta records are required evidence to verify merge readiness, capture system impact, and ensure safe code rollback during Gate 5, 5.5, and 6 reviews.

Related Skills

Explore More Software Engineering Skills→
vladm3105vladm3105
16

doc-bdd

Generate Layer-4 BDD test scenarios in Gherkin Given-When-Then format.

Community
Advanced
arbisoftarbisoft
4

canary-watch

Monitor deployed URLs for regressions across HTTP status, console errors, network failures, performance metrics, content integrity, and API health.

Official
Advanced
thec3ukthec3uk

Global Commenting

Validate and enforce global commenting standards across Claude Code projects.

Official
Basic
nishantnaagnihotrinishantnaagnihotri

build-merge-gate-orchestration

Coordinates build, runtime QA, and merge readiness gates across issues and PRs.

Community
Advanced