implementation-runner — community implementation-runner, moon-bot, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing automated code change implementation and recording capabilities. Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation.

munlucky munlucky
[0]
[0]
Updated: 2/2/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
51
Canonical Locale
en
Detected Body Locale
en

Perfect for Development Agents needing automated code change implementation and recording capabilities. Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation.

Core Value

Empowers agents to automate code changes and recording across multiple technologies, supporting capabilities like change scope definition, implementation, and key change summary recording, utilizing files and artifacts from the repository and context documents in formats like YAML.

Ideal Agent Persona

Perfect for Development Agents needing automated code change implementation and recording capabilities.

↓ Capabilities Granted for implementation-runner

Automating code changes for multiple technologies
Recording and summarizing key changes in repository files
Updating implementation completion status in analysis context

! Prerequisites & Limits

  • Requires access to analysis context and repository files
  • Needs specific artifacts like context documents and open files
  • Limited to technologies and file formats supported by the implementation runner

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is implementation-runner?

Perfect for Development Agents needing automated code change implementation and recording capabilities. Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation.

How do I install implementation-runner?

Run the command: npx killer-skills add munlucky/moon-bot/implementation-runner. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for implementation-runner?

Key use cases include: Automating code changes for multiple technologies, Recording and summarizing key changes in repository files, Updating implementation completion status in analysis context.

Which IDEs are compatible with implementation-runner?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for implementation-runner?

Requires access to analysis context and repository files. Needs specific artifacts like context documents and open files. Limited to technologies and file formats supported by the implementation runner.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add munlucky/moon-bot/implementation-runner. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use implementation-runner immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

implementation-runner

Install implementation-runner, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Implementation Runner

Inputs

  • analysisContext.request.userMessage
  • analysisContext.decisions.skillChain
  • analysisContext.repo.openFiles
  • analysisContext.artifacts.contextDocPath (if present)

Procedure

  1. Check requirements and context.
  2. Define change scope and implement.
  3. Record changed files and key change summary.
  4. Update implementation completion in analysisContext.

Output (patch)

yaml
1signals.implementationComplete: true
2repo.changedFiles:
3  - src/...
4notes:
5  - "implementation: complete, changed_files=3"

Rules

  • Do not call other skills/subagents.
  • If failed or deferred, record the reason in notes.

Related Skills

Looking for an alternative to implementation-runner or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer