arib-wave-end

Audit development waves, generate stakeholder reports, and manage secure branch merges.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-wave-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arib-wave-end
Source: https://github.com/AribSudia/claude-code-methodology/tree/main/.claude/skills/arib-wave-end
Command: npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-wave-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent project delivery and unverified code merges by enforcing a rigorous, automated gate-keeping process at the end of a development wave.

Core Features & Use Cases

  • Deep Audit Gate: Executes a 21-section audit to ensure code quality, security, and compliance before any merge occurs.
  • Automated Reporting: Generates a stakeholder-ready report summarizing shipped features, audit results, and remaining risks.
  • Fail-Safe Merging: Automatically manages PR creation and merging only after all verification agents and audit gates return a passing status.

Quick Start

Run the arib-wave-end skill to audit the current wave, generate the stakeholder report, and trigger the automated merge process.

Frequently Asked Questions about arib-wave-end

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

FAQPage Schema
How do I automate git branch merges with an audit trail for compliance?

Automate git branch merges with an audit trail by executing a multi-section audit gate that verifies code quality and compliance before authorizing secure branch integration. This fail-safe process ensures no unverified code is merged.

What is a development wave audit gate and when do I need it?

A development wave audit gate is an automated verification process that executes a 21-section audit to ensure code quality, security, and compliance before finalizing a development cycle. You need it for workflows requiring strict audit-trail maintenance.

Does automated wave finalization require GitHub CLI and a project ledger system?

Automated wave finalization requires integration with git, GitHub CLI, and a project-specific ledger system. These dependencies are necessary to validate wave completion, authorize code integration, and manage secure branch merges.

How do I generate stakeholder reports for shipped features and remaining risks?

Generate stakeholder reports for shipped features and remaining risks by running an automated finalization process that summarizes audit results and compliance status. This creates a stakeholder-ready report during the secure merge process.

Can I enforce CI-CD quality gates to prevent unverified code merges?

Enforce CI-CD quality gates to prevent unverified code merges by applying an automated gate-keeping process at the end of a development wave. It only triggers PR creation and merging after all verification agents return a passing status.

What are the limitations of automated compliance audits for secure branch merges?

Automated compliance audits for secure branch merges are limited by their dependency on git, GitHub CLI, and a project-specific ledger system. The fail-safe merging process halts if any verification agent or audit gate returns a failing status.