implement

Automate GitHub issue implementation through verification gates and pull request creation.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/evanharmon1/harmon-devkit --skill implement-evanharmon1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/universal/implement
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill implement-evanharmon1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead and inconsistency involved in moving a claimed GitHub issue through the development lifecycle, ensuring that every PR is fully verified, linted, and ready for maintainer review.

Core Features & Use Cases

  • Automated Dev Loop: Orchestrates the entire implementation process, including branching, linting, verification, and second-model review.
  • Gate Enforcement: Automatically runs repository-specific gates (linting, CI, definition-of-done) to ensure code quality before PR creation.
  • Shepherd Integration: Manages the transition from draft PR to ready-for-review status by tracking checks and settling deferred findings.

Quick Start

Invoke the implement skill by providing the issue number or URL to begin the automated development workflow for that specific task.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate a GitHub issue implementation from claim to ready-for-review PR?

Automated GitHub issue implementation coordinates branching, linting, local development loops, and pull request creation through GitHub CLI. It enforces repository-specific commit conventions and testing gates, producing a fully verified PR ready for maintainer review.

What is an automated dev loop for pull request creation?

An automated dev loop orchestrates the entire implementation process for a claimed issue, including branch creation, linting, verification, and second-model review. It ensures every PR meets repository-specific quality standards before reaching maintainer review.

How do I enforce definition-of-done and linting gates before creating a GitHub pull request?

Gate enforcement automatically runs repository-specific checks such as linting, CI, and definition-of-done validation before PR creation. This ensures code quality standards are met deterministically, preventing unverified code from reaching the review stage.

Can I use GitHub CLI to manage branch creation and PR lifecycle tracking automatically?

GitHub CLI integration enables deterministic task execution including branch management, gate verification, and automated PR lifecycle tracking. It manages transitions from draft to ready-for-review status by tracking checks and settling deferred findings.

Does automated issue implementation work with repository-specific commit conventions and testing standards?

Automated issue implementation enforces strict adherence to repository-specific commit conventions and testing standards. It applies these gates during local development loops, ensuring every PR meets project-specific requirements before submission.

Why does my automated pull request workflow fail gate verification before review?

Gate verification fails when repository-specific checks such as linting, CI, or definition-of-done validation detect issues during the development loop. The automated workflow blocks PR creation until all gates pass, ensuring only verified code reaches review.