From nexus-agents
Processes open GitHub issues using self-development protocol, prioritizing research registry techniques with voting and testing. For dogfooding workflows, issue implementation, or research techniques.
npx claudepluginhub williamzujkowski/nexus-agentsThis skill is limited to using the following tools:
<!-- CANONICAL SOURCES:
Grooms all open GitHub issues with subagents for clarity then loops implementation: branch, research, swarm code, test, commit, merge PRs until backlog cleared.
Resolves GitHub issues via 8-phase workflow: fetch details, analyze requirements, implement solutions, verify correctness, code review, commit changes, create PRs. Activates on resolve, implement, fix requests or issue references.
Resolves GitHub issues through triage, root cause analysis, TDD, branch management, testing, and CI/CD-compliant pull requests. Ideal for team workflows on bugs and features.
Share bugs, ideas, or general feedback.
Process open issues following the self-development protocol.
Full workflows:
TZ='America/New_York' date '+%Y-%m-%d %H:%M:%S %Z'
git status --short
gh issue list --state open --limit 20
grep -A 5 "status: planned" docs/research/registry/techniques.yaml | \
grep -B 5 "priority: P[12]"
Priority order:
Follow CONTRIBUTION_GUIDE.md:
status: planned → status: implementedSee CODING_STANDARDS.md:
| Excuse | Counter |
|---|---|
| "Pick the easy issue first" | Easy + un-implemented is suspicious — usually means the issue isn't actually easy or the spec is wrong. Pick by impact, not by ease. |
| "Skip the research check" | The research registry is where prior thought lives. Skipping it means re-deriving solutions and missing prior decisions. |
| "Test coverage 80% is fine" | Per CLAUDE.md, the gate is 89.66% / 93.26% (statement / function). Don't ship below the existing floor. |
| "Implementation is partial — flag mark as 'in progress'" | Per implement-feature: don't mark implemented if partial. Either ship the slice or split the issue. |
status: implementedimplemented