create-code

Implement code from a validated plan file with linters and tests.

1|Updated Dec 22, 2017

Search Tags:#testing #tdd #linting #development workflow #code generation #implementation

Ready to run

npx skills add https://github.com/coreyhulen/enviroment --skill create-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-code
Source: https://github.com/coreyhulen/enviroment/tree/main/claude-init/skills/create-code
Command: npx skills add https://github.com/coreyhulen/enviroment --skill create-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the implementation of code based on a pre-defined plan, ensuring that development follows a structured and validated process.

Core Features & Use Cases

Plan-driven Implementation: Executes code changes strictly based on tasks outlined in a specified plan file.
Quality Assurance: Integrates linters and tests to verify code quality and functionality before completion.
Workflow Integration: Seamlessly fits into a larger development cycle, following /create-plan and preceding /review-code.
Use Case: After creating a plan for a new user authentication feature, use this Skill to write the necessary backend and frontend code, including writing and running tests, and ensuring code style compliance.

Quick Start

Implement the code described in the plan file named 'implementation-plans/user-auth.md'.

Frequently Asked Questions about create-code

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

FAQPage Schema

How do I implement code from a plan file while following TDD workflows?▼

Code implementation from a plan file follows TDD workflows by executing tasks sequentially, integrating linters, and running tests to verify quality against acceptance criteria. This ensures development adheres to technical specifications and validates functionality before completion.

What is plan-driven code implementation and when do I need it?▼

Plan-driven code implementation automates writing code based on a pre-defined plan file, ensuring structured development. You need it when executing validated tasks sequentially to maintain adherence to technical specifications and quality assurance standards.

Can I use linters and tests to verify code quality during implementation?▼

Yes, linters and tests integrate directly into the code implementation process to verify quality and functionality. They execute alongside sequential task processing to ensure code style compliance and validate acceptance criteria before completion.

What happens if no specific plan file is provided for code generation?▼

When no specific plan file is provided, the code generation process handles plan discovery and prompts user confirmation. This ensures the implementation targets the correct validated plan before executing any sequential code changes.

Does plan-based implementation work with existing development workflows?▼

Plan-based implementation integrates seamlessly into development workflows by following plan creation and preceding code review. It executes code changes sequentially based on tasks outlined in a specified plan file, fitting into the larger development cycle.

Why does code implementation require a validated plan file?▼

Code implementation requires a validated plan file to ensure development follows a structured process. This plan-driven approach guarantees sequential task execution adheres to acceptance criteria and technical specifications, preventing unstructured code generation.