code-assist

Guide teams through TDD-based Explore, Plan, Code, and Commit workflows.

11|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/brazil-bench/pourpoise --skill code-assist-brazil-bench
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-assist
Source: https://github.com/brazil-bench/pourpoise/tree/main/skills/code-assist
Command: npx skills add https://github.com/brazil-bench/pourpoise --skill code-assist-brazil-bench

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This SOP provides a structured approach to implementing code tasks using test-driven development (TDD). It acts as a Technical Implementation Partner and TDD Coach, guiding teams to design tests first, plan the work, code with idiomatic patterns, and commit changes in a traceable workflow. It emphasizes readability, extensibility, and alignment with existing project conventions across languages.

Core Features & Use Cases

  • Guided Explore, Plan, Code, Commit workflow that aligns with existing package patterns.
  • Automatic generation of test cases and implementation scaffolds to drive development in Python, Swift, and other languages.
  • Collaborative guidance with options for interactive or auto modes, with clear documentation artifacts.
  • Supports integration with current repository structures, emphasizing maintainability and clean handoffs.

Quick Start

Describe your task_description and the assistant will guide you through Explore, Plan, Code, and Commit steps, generating tests, code skeletons, and commit-ready changes.

Frequently Asked Questions about code-assist

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

FAQPage Schema
How do I implement test-driven development across different programming languages?

Test-driven development across languages is implemented through a structured Explore, Plan, Code, and Commit workflow. This process generates test scaffolds and idiomatic code skeletons first, ensuring maintainability and alignment with existing project conventions.

What is the best way to scaffold tests before writing implementation code?

The best way to scaffold tests is using a guided workflow that automatically generates test cases and implementation skeletons. This test-first approach drives development by planning artifacts and structuring code patterns before the actual logic is written.

Can I use a structured coding workflow with my existing repository conventions?

Yes, this structured coding workflow integrates directly with current repository structures. It emphasizes maintainability by aligning new test scaffolding and implementation patterns with your project's existing package conventions and cross-language design.

How do I plan and document software engineering tasks for clean handoffs?

Software engineering tasks are planned and documented using a structured workflow that generates clear documentation artifacts. This collaborative guidance produces planning artifacts, test scaffolding, and traceable commit-ready changes for clean team handoffs.

Does test-driven development guidance support both interactive and automated modes?

Test-driven development guidance supports both interactive and automated modes. Teams can choose collaborative guidance throughout the Explore, Plan, Code, and Commit phases, allowing flexibility in how structured documentation and code artifacts are generated.

When should I not use a guided test-first coding workflow?

A guided test-first coding workflow may not suit projects requiring rapid prototyping without traceable documentation or strict planning artifacts. If your task bypasses standard repository conventions or lacks clear test requirements, this structured approach adds unnecessary overhead.