bk-verify

Name: bk-verify
Availability: InStock
Author: dikini

Audit code implementations against specifications by verifying traceability markers and detecting gaps.

Updated Mar 3, 2026

Search Tags:#code review #verification #compliance #auditing #traceability #spec compliance

Ready to run

npx skills add https://github.com/dikini/knot --skill bk-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bk-verify
Source: https://github.com/dikini/knot/tree/main/.agents/skills/bk-verify
Command: npx skills add https://github.com/dikini/knot --skill bk-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately reflect their defined specifications, preventing bugs and compliance issues before they reach production.

Core Features & Use Cases

Traceability Verification: Automatically checks if code markers (SPEC-XXX, TASK-XXX) correspond to actual definitions in documentation.
Gap Detection: Identifies missing implementations, untested requirements, and orphaned code markers.
Use Case: Before merging a pull request, run this Skill to confirm all new features and bug fixes are fully implemented and tested according to the project's specifications, ensuring release readiness.

Quick Start

Run a full verification of the current component against its specifications.

Frequently Asked Questions about bk-verify

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

FAQPage Schema

How do I verify code compliance against specifications before a release?▼

Traceability verification checks if code markers (SPEC-XXX, TASK-XXX) correspond to actual definitions in documentation. It identifies missing implementations, untested requirements, and orphaned markers to ensure accurate code reflections of specifications.

Can I generate a compliance matrix for a pull request review?▼

Yes, a compliance matrix can be built during pull request reviews by validating marker IDs against specifications. This process confirms all new features and bug fixes are fully implemented and tested according to project requirements.

What is the best way to detect orphaned code markers and spec gaps?▼

Detecting orphaned code markers and spec gaps requires auditing code implementation against defined specifications. This process automatically identifies missing implementations and untested requirements lacking proper traceability markers.

Does spec compliance auditing support JSON format reporting?▼

Spec compliance auditing supports reporting findings in summary, detailed, or JSON formats. This allows integration into automated release readiness workflows and pre-commit checks for continuous compliance verification.

When do I need traceability marker validation in my development workflow?▼

Traceability marker validation is needed for pre-commit checks, pull request reviews, release readiness, and compliance verification workflows. It prevents bugs and compliance issues by ensuring code accurately reflects defined specifications before production.