dogfooding-issues

Process open GitHub issues with research-registry prioritization and TDD coverage gates.

18|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/nexus-substrate/nexus-agents --skill dogfooding-issues-nexus-substrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfooding-issues
Source: https://github.com/nexus-substrate/nexus-agents/tree/main/skills/dogfooding-issues
Command: npx skills add https://github.com/nexus-substrate/nexus-agents --skill dogfooding-issues-nexus-substrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you process open GitHub issues using a self-development protocol so improvements are properly researched, tested, registered, and verified rather than shipped as unvalidated changes.

Core Features & Use Cases

  • Research registry–first selection: Picks issues based on technique status and priority from the research registry (e.g., planned items with P1/P2 priorities).
  • TDD + contribution workflow: Enforces an interface-first approach and test-driven development, then updates the registry status when implementation is complete.
  • Dogfooding governance and quality gates: Applies quality checks aligned with established coverage gates and flags red cases like partial, flag-gated implementations or missing registry updates.
  • Red-flag detection for scope drift: Warns when an issue produces excessive follow-ups, indicating likely scope creep.

Quick Start

Ask your AI to process open GitHub issues for dogfooding by following the self-development protocol and ensuring the research registry and tests are updated before closing.

Frequently Asked Questions about dogfooding-issues

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

FAQPage Schema
How do I process open GitHub issues using a test-driven development workflow?

To process open GitHub issues with TDD, this Skill applies a self-development protocol that enforces interface-first design, test coverage gates, and research-registry updates before verifying closure with PR-linked summaries.

What is a research registry and how does it prioritize issue processing?

A research registry tracks technique status and priority levels like P1 or P2 to drive issue selection, ensuring planned items are selected first and registry status transitions are validated upon implementation completion.

How do I enforce test coverage gates when implementing bug fixes from GitHub issues?

Test coverage gates are enforced by applying test-driven development with interface-first design, flagging partial or flag-gated implementations as red cases during the dogfooding governance and quality checks.

When should I worry about scope creep when addressing open issues?

Scope creep occurs when an issue produces excessive follow-ups, triggering red-flag detection warnings that indicate likely scope drift during the issue-to-PR development workflow.

Can I use this protocol to implement research techniques alongside bug fixes?

Yes, the self-development protocol applies to implementing research techniques, addressing bugs, and following dogfooding workflow tasks across issue-to-PR development with proper registry status transitions.

What is the best way to ensure GitHub issues are properly researched before shipping fixes?

The best way is using a research-registry driven prioritization protocol that validates interface design, enforces TDD coverage, updates registry status, and verifies closure with PR-linked summaries to prevent unvalidated changes.