skills.rest
kekemoto
kekemotoCOMMUNITY
Explore all skills by this author →
Website𝕏@keke_motoGitHub

harness-coder

Automate sequential spec implementation with acceptance criteria, testing, and commits in a feature branch.

Updated Jun 6, 2026
Search Tags:#automation#git#workflow#development#specifications#pull-request
One-click install
npx skills add https://github.com/kekemoto/skills --skill harness-coder-kekemoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-coder
Source: https://github.com/kekemoto/skills/tree/main/skills/harness-coder
Command: npx skills add https://github.com/kekemoto/skills --skill harness-coder-kekemoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of manual, repetitive implementation of development specifications by automating the end-to-end flow from acceptance criteria verification to feature branch creation and PR submission.

Core Features & Use Cases

  • Sequential Implementation: Automatically drives specs in filename-number order, ensuring dependencies are respected.
  • Integrated Workflow: Handles the entire lifecycle of a feature branch, including pre-flight checks, commit generation, and final PR creation.
  • Use Case: When you have a project with multiple defined specs in a directory, use this skill to implement them one by one, verify the results, and prepare a single, clean pull request for the main branch.

Quick Start

Invoke the harness-coder skill by running the command slash harness-coder followed by your project slug to begin the automated implementation process.

Frequently Asked Questions about harness-coder

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

FAQPage Schema
How do I automate sequential spec implementation and pull request creation?▼

Automating sequential spec implementation drives acceptance criteria, testing, and commit generation within a dedicated feature branch. It reads pre-defined specifications in filename-number order, ensuring dependencies are respected before submitting a clean pull request.

What is the best way to implement development specifications in filename order?▼

Implementing development specifications in filename order requires an automated workflow that processes specs sequentially. This approach handles the entire feature branch lifecycle, from pre-flight checks and commit generation to final pull request creation, without manual intervention.

Do I need local test runner compatibility to automate git workflow integration?▼

Local test runner compatibility is required to automate git workflow integration for specifications. The automated process relies on local testing to ensure code quality and error-checked execution before generating commits and managing feature branches.

Can I use automated spec implementation with a pre-defined project directory?▼

Automated spec implementation applies directly to software development workflows where project specifications are pre-defined in a directory. The system systematically executes these defined specs, verifies acceptance criteria, and prepares a single pull request for the main branch.

Why does automated pull request generation require a dedicated feature branch?▼

Automated pull request generation requires a dedicated feature branch to isolate systematic, error-checked execution. This branch management approach ensures that sequential commits and acceptance criteria verification do not impact the main branch until the final review.

Related Skills

Explore More Software Engineering Skills→
MeechYourGoalsMeechYourGoals
2

using-git-worktrees

Create isolated Git worktrees with dependency installation and baseline tests.

Community
Advanced
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
k97k97
4

finishing-a-development-branch

Verify tests before merging or cleaning up git development branches.

Community
Intermediate
gckogcko
1

create-pr

Run tests, lint, commit, push, and open a pull request against main.

Community
Intermediate