run

Execute GitHub issue steps sequentially with targeted tests and conventional commits.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill run-ryan-mahoney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/run
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill run-ryan-mahoney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the execution of a GitHub issue spec by applying the requested steps to the current codebase in a safe, low-risk manner, reducing manual task load.

Core Features & Use Cases

  • Sequential step execution: accepts one or more steps and applies them in order with clear confirmations.
  • Targeted testing & commits: runs targeted tests for changed behavior and creates conventional commits for each step.
  • Issue-guided automation: orchestrates changes directly from issue descriptions, ensuring traceability to the original spec.

Quick Start

Provide the GitHub issue number and the step(s) you want implemented and the AI will perform them in sequence.

Frequently Asked Questions about run

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

FAQPage Schema
How do I automate GitHub issue spec execution against my codebase?

Automating GitHub issue execution requires sequentially applying described steps as surgical, low-risk codebase changes, running targeted tests, and creating conventional commits. This skill orchestrates that exact workflow directly from the issue specification.

Can I execute multiple steps from a GitHub issue sequentially?

Yes, executing multiple steps sequentially is supported. The skill accepts one or more steps from a GitHub issue and applies them in order with clear step boundaries and notifications between each sequential codebase change.

How does issue-guided automation handle testing and commits?

Issue-guided automation handles testing by running targeted tests specifically for changed behavior, then creating a conventional commit for each completed step to ensure traceability back to the original GitHub issue specification.

Does this automation tool apply large modifications to the codebase?

No, this automation tool does not apply large modifications. It applies only surgical, low-risk changes to the codebase, ensuring safe execution when applying steps described in a GitHub issue specification.

What is the best way to ensure traceability when executing issue specs?

The best way to ensure traceability when executing issue specs is to orchestrate changes directly from the GitHub issue description and commit each step with a conventional message, linking the applied codebase changes back to the original spec.