zoo-code-impl

Implement the smallest code change for an approved Zoo subtask plan.

5|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/andreyvit/zoo --skill zoo-code-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoo-code-impl
Source: https://github.com/andreyvit/zoo/tree/main/.codex/skills/zoo-code-impl
Command: npx skills add https://github.com/andreyvit/zoo --skill zoo-code-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to implement the smallest correct code change for an approved Zoo active-subtask plan, ensuring compliance with tests and architectural constraints.

Core Features & Use Cases

  • Smallest-change principle: implement only what is necessary to pass tests while preserving architecture.
  • Follow the approved tactical plan for the active next subtask.
  • Search for existing implementation paths, run tests, and avoid unnecessary refactors.
  • Use Case: when a subtask requires a minimal, auditable change that won't destabilize the codebase.

Quick Start

Implement the smallest change that passes tests for the active Zoo subtask.

Frequently Asked Questions about zoo-code-impl

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

FAQPage Schema
How do I implement the smallest correct code change for an approved subtask plan?

To implement the smallest correct code change, follow the approved tactical plan for the active subtask, search for existing implementation paths, and make only the minimal edits necessary to pass tests while preserving architecture.

What is the smallest-change principle in code modification?

The smallest-change principle means implementing only what is necessary to pass tests while preserving architecture. It avoids unnecessary refactors to ensure minimal risk edits and safe integration within the development workflow.

How do I validate code changes without destabilizing the codebase?

You validate code changes by running tests against the minimal edits and adhering strictly to architectural constraints. This ensures the modification is auditable and won't destabilize the codebase during integration.

When should I avoid refactoring during subtask implementation?

You should avoid refactoring during subtask implementation when the goal is a minimal, auditable change. Unnecessary refactors introduce risk; instead, search for existing implementation paths and apply only what is required to pass tests.

Does the Zoo subtask framework require a tactical plan before coding?

Yes, the Zoo subtask framework requires an approved active-subtask plan before coding. You must follow this tactical plan to ensure strict adherence to tests and architecture during implementation.

What's the best way to ensure safe code integration within the Zoo subtask framework?

The best way to ensure safe code integration is to deliver the smallest correct code change for the approved Zoo active-subtask plan, running tests to validate minimal risk edits and strict architectural compliance.