auto-coder

Automate spec-driven TypeScript feature development with tests and atomic commits.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ys0714/ecom-agent --skill auto-coder
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: auto-coder
Source: https://github.com/ys0714/ecom-agent/tree/main/.claude/skills/auto-coder
Command: npx skills add https://github.com/ys0714/ecom-agent --skill auto-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The auto-coder automates the repetitive and error-prone work of converting a project's written specification into implemented TypeScript features, tests, and atomic commits so maintainers can move MVP tasks forward reliably.

Core Features & Use Cases

  • Spec synchronization: Keeps PROJECT_SPEC.md in sync with chaptered reference files to ensure implementation follows the canonical spec.
  • Task discovery and implementation: Identifies the next pending MVP task (or a specified task ID), plans file changes according to the project's architecture, writes TypeScript ESM code consistent with existing patterns, and adds corresponding Vitest tests.
  • Autonomous test-and-fix loop: Runs TypeScript type checks and Vitest with up to three auto-fix rounds, stops and reports if unresolved, and persists progress by updating the spec and preparing atomic git commits.
  • Use case: Perfect for maintainers of the ecom-agent repository who want a controlled, reproducible autopilot to implement small-to-medium scoped features from PROJECT_SPEC.md while preserving project conventions and traceability.

Quick Start

Run the auto-coder to sync PROJECT_SPEC.md, pick the next pending task, implement code following project patterns, run tests with up to three auto-fix attempts, and prepare an atomic commit for confirmation.

Frequently Asked Questions about auto-coder

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

FAQPage Schema
How do I automate TypeScript feature implementation from a project spec?โ–ผ

Automating TypeScript feature implementation from a project spec involves syncing PROJECT_SPEC.md, identifying the next pending MVP task, and autonomously generating ESM code with Vitest tests. The tool runs type checks and auto-fixes before preparing an atomic git commit.

How does spec-driven development keep code synchronized with my project specification?โ–ผ

Spec-driven development keeps code synchronized by syncing PROJECT_SPEC.md with chaptered reference files before implementation. This ensures the generated TypeScript code follows the canonical spec, and updates the spec and git state atomically upon task completion.

Can I autonomously generate Vitest tests for Node.js ESM projects?โ–ผ

You can autonomously generate Vitest tests for Node.js ESM projects by applying a spec-driven automation tool. It writes TypeScript ESM code consistent with existing project patterns, adds corresponding Vitest tests, and runs up to three auto-fix rounds to resolve test failures.

What is the best way to automate atomic git commits for TypeScript MVP tasks?โ–ผ

Automating atomic git commits for TypeScript MVP tasks is best handled by an autonomous spec-driven workflow. It implements the next pending task from PROJECT_SPEC.md, runs tsc and Vitest with up to three auto-fix rounds, and prepares an atomic git commit to persist progress reliably.

Does the automated test-and-fix loop stop if TypeScript type checks fail?โ–ผ

The automated test-and-fix loop stops if TypeScript type checks remain unresolved. It runs tsc and Vitest with up to three auto-fix rounds; if errors persist, the process stops and reports the issue without updating the spec or preparing a commit.

Do I need a specific repository structure to run spec-driven TypeScript automation?โ–ผ

Spec-driven TypeScript automation requires a Node.js ESM project structure like the ecom-agent repository. You need a PROJECT_SPEC.md file and chaptered reference files to ensure the generated code and tests correctly follow your project's architecture and ESM import rules.