implementation-runner

Execute planned implementation steps and record changed files in analysisContext.

Updated Jan 4, 2026

Search Tags:#automation #logging #implementation #patch #code-changes #analysiscontext

Ready to run

npx skills add https://github.com/munlucky/claude-command-relay --skill implementation-runner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-runner
Source: https://github.com/munlucky/claude-command-relay/tree/main/.claude/skills/implementation-runner
Command: npx skills add https://github.com/munlucky/claude-command-relay --skill implementation-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates actual implementation steps within a chain and records completion status plus changed files into the analysisContext for traceability and auditability.

Core Features & Use Cases

Executes the planned implementation steps for a given user request within the chain.
Tracks and records changed files, and summarizes key changes into the analysis context.
Provides clear failure handling and prevents unintended skill interactions by documenting results in analysisContext.

Quick Start

Run the implementation runner on a prepared analysis context to perform the planned changes and capture the resulting patch.

Frequently Asked Questions about implementation-runner

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

FAQPage Schema

How do I automate in-repo code changes and generate a patch for review?▼

To automate in-repo code changes and generate a patch for review, use an implementation runner to execute planned steps, track changed files, and output a patch list. It records the final completion status and notes directly in the analysisContext for traceability.

How does logging implementation outcomes in analysisContext work?▼

Logging implementation outcomes in analysisContext works by automatically summarizing key code changes and recording the final completion status into the context object. This provides clear failure handling and prevents unintended interactions by documenting results centrally for auditability.

Can I use an implementation runner in a chain-based workflow to track changed files?▼

Yes, you can use an implementation runner in a chain-based workflow to track changed files. It is specifically designed for chain workflows where a user request requires applying changes, automatically recording the changed files and generating a patch for review.

Do I need external automation tools to execute real implementations within my repository?▼

No, you do not need external automation tools to execute real implementations within your repository. The implementation runner enforces no external skill invocations, coordinating actual implementation steps internally and recording the completion status directly into the analysisContext.

What are the limitations of using an implementation runner for code changes?▼

Limitations of using an implementation runner for code changes include its enforcement of no external skill invocations, restricting interactions to the prepared analysis context. It strictly handles in-repo implementations and outputs a patch list, requiring a pre-existing chain workflow to function properly.