code-assist

Implement code tasks with test-driven development in an Explore-Plan-Code-Commit workflow.

3.1k|286|Updated Sep 7, 2025
One-click install
npx skills add https://github.com/mikeyobrien/ralph-orchestrator --skill code-assist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-assist
Source: https://github.com/mikeyobrien/ralph-orchestrator/tree/main/.claude/skills/code-assist
Command: npx skills add https://github.com/mikeyobrien/ralph-orchestrator --skill code-assist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.

Core Features & Use Cases

  • Guided Explore-Plan-Code-Commit workflow for code tasks.
  • Acts as a technical partner and TDD coach to balance automation with human collaboration.
  • Provides templates, patterns, and best practices to produce clean, maintainable code.

Quick Start

Use the code-assist skill to guide implementing a feature with a TDD-driven workflow from task description to plan, code, and commit.

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 for a new feature from scratch?

Test-driven development for a feature is guided through an Explore-Plan-Code-Commit workflow that enforces planning, writes automated tests first, and produces incremental commits to ensure idiomatic, maintainable code.

What is the Explore-Plan-Code-Commit workflow for software engineering tasks?

The Explore-Plan-Code-Commit workflow is a structured process for code tasks that involves exploring requirements, planning implementation, writing code with automated testing, and committing changes incrementally across feature development or refactoring.

Can I use a TDD workflow for bug fixes and refactoring existing code?

Yes, a TDD-driven workflow supports bug fixes and refactoring by applying structured planning and automated testing to ensure changes follow existing patterns, avoid over-engineering, and maintain code quality.

What's the best way to structure code tasks to avoid over-engineering?

The best way to avoid over-engineering is using a Technical Implementation Partner approach that follows existing patterns, balances automation with human collaboration, and produces clean, modern code through structured TDD workflows.

Does this TDD workflow support custom scripts and reference directories?

Yes, the workflow recognizes optional directories including scripts/, references/, and assets/ to support execution, and it enforces a YAML frontmatter with name and description for operational instructions.

When should I not use a structured TDD workflow for code implementation?

A structured TDD workflow may not suit tasks lacking clear planning requirements or automated testing needs, as it enforces an Explore-Plan-Code-Commit process designed for incremental commits and structured software engineering tasks.