rdr-accept

Accept RDRs after gate pass and update frontmatter status.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Hellblazer/nexus --skill rdr-accept
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rdr-accept
Source: https://github.com/Hellblazer/nexus/tree/main/nx/skills/rdr-accept
Command: npx skills add https://github.com/Hellblazer/nexus --skill rdr-accept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the formal acceptance of RDRs after they have passed the gate, ensuring decisions are documented, tracked, and ready for implementation.

Core Features & Use Cases

  • Verify gate results and update the RDR status to accepted with an acceptance date.
  • Regenerate project READMEs or indices to reflect the accepted RDRs.
  • Stage and commit changes to keep the repository in sync with governance decisions.

Quick Start

Accept the RDR after gate PASSED by confirming the gate status and updating the RDR frontmatter.

Frequently Asked Questions about rdr-accept

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

FAQPage Schema
How do I update RDR frontmatter to mark a decision as accepted after a gate passes?

After a gate passes, this skill updates RDR frontmatter to status: accepted, records the accepted_date, and stages the changes for commit to maintain repository metadata consistency.

What is the process for accepting an RDR and regenerating documentation indices?

Accepting an RDR involves verifying the gate result, updating frontmatter metadata, and regenerating the relevant README index to reflect the newly accepted governance decisions before staging file changes.

Do I need a gate PASSED status before I can accept an RDR?

Yes, this skill confirms the gate status is PASSED before it updates the RDR frontmatter to accepted and records the acceptance date in the repository.

How does accepting an RDR keep the repository README in sync with governance decisions?

Accepting an RDR regenerates the relevant README index and stages changes for commit using filesystem writes, ensuring end-to-end state consistency between the gate result, repository metadata, and documentation.

What's the best way to automate RDR acceptance and frontmatter updates in a git workflow?

Automating RDR acceptance is handled by updating frontmatter status, recording the accepted_date, regenerating README indices, and staging changes for commit to maintain end-to-end state consistency across the repository.