nurture

Review and fix code implementations for correctness and test coverage.

2|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Epiphytic/brains --skill nurture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nurture
Source: https://github.com/Epiphytic/brains/tree/main/skills/nurture
Command: npx skills add https://github.com/Epiphytic/brains --skill nurture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nurture identifies gaps in implementations, tests, and integration, then systematically fixes bugs, adds missing tests, and documents partial work so shipped code meets the design spec and quality expectations.

Core Features & Use Cases

  • Phase-scoped reviews: Focus reviews on files changed in a plan phase or run a full-project review when invoked standalone.
  • Automated fixes and testing: Iterate on P0/P1 issues with targeted fixes, run tests after each change, and commit atomically.
  • Multi-LLM review modes: Support single-agent review, parallel council review, or multi-round debate for deeper deliberation and consensus.
  • Operational duties for teammates: When invoked by a phase-3 teammate, ensure commits, update .gitignore, reflect half-complete state in docs, and file follow-up task items.
  • Use Case: After an implementation sprint, run nurture to find correctness bugs, add end-to-end tests, and produce a nurture report with commits and follow-up tasks.

Quick Start

Ask the nurture skill to review and fix recent changes, produce a prioritized issue list, and apply approved fixes with tests and commits.

Frequently Asked Questions about nurture

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

FAQPage Schema
How do I review and fix code changes for correctness and test coverage?

To review and fix code changes for correctness and test coverage, run automated code reviews that identify implementation gaps, apply targeted fixes to prioritized issues, execute tests after each change, and commit the updates atomically.

What is the best way to automate bug fixes and add missing tests after a sprint?

Automating bug fixes and adding missing tests after a sprint requires running a systematic code review that iterates on prioritized issues, adds end-to-end tests, and produces a report with commits and follow-up task items.

Can I scope code reviews to only the files changed in a specific git commit?

Yes, you can scope code reviews to only the files changed in a git commit by running phase-scoped reviews that focus on changed files, or you can run a full-project review when invoked standalone.

Does multi-LLM debate review improve code quality assurance over single-agent review?

Multi-LLM debate review improves code quality assurance by supporting parallel council review or multi-round debate for deeper deliberation and consensus, compared to standard single-agent review modes.

How do I document partial work and file follow-up tasks for incomplete code implementations?

To document partial work and file follow-up tasks for incomplete implementations, invoke operational duties during a phase-3 review to reflect the half-complete state in docs, update .gitignore, and file follow-up task items.

When should I avoid running automated refactor and quality assurance reviews?

You should avoid running automated refactor and quality assurance reviews when there are no defined design specs to validate against, as the process relies on comparing implementations against expected design specifications and quality expectations.