work

Automate GitHub issue architectural changes with commits per module.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/dallenpyrah/pi --skill work-dallenpyrah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/dallenpyrah/pi/tree/main/skills/work
Command: npx skills add https://github.com/dallenpyrah/pi --skill work-dallenpyrah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill addresses the complex and time-consuming task of executing code changes from a GitHub issue directly on the current branch, with tasks being derived from the issue's modules section.

Core Features & Use Cases

  • GitHub Issue Parsing: Extracts architecture and tasks from the Modules section of a GitHub issue.
  • Code Committing: Automates code commits that reference the issue number for easy traceability.
  • Branch Safety Check: Ensures the work is done on non-prod branches, maintaining branch integrity.
  • Error Handling: Provides clear feedback for preconditions like branch safety and issue presence.
  • Sub-Agent Execution: Uses sub-agents for specific tasks within a module.

Quick Start

To execute architecture tasks from issue 42, use: /work 42.

Frequently Asked Questions about work

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

FAQPage Schema
How do I automate GitHub issue execution and commit code changes per issue module?

Automate GitHub issue execution by parsing the issue's Modules section and using sub-agent processing to commit code changes per module directly on your current branch. Simply invoke the work command with the issue number to start automated architectural execution.

How does automated code committing reference the original GitHub issue for traceability?

Automated code commits reference the original GitHub issue by embedding the issue number directly in the commit message. This ensures full traceability between the architectural changes applied and the source issue that defined the tasks.

Does the work Skill operate safely on production branches when executing GitHub issue tasks?

No, the work Skill enforces branch safety by ensuring GitHub issue execution only happens on non-prod branches. This maintains production branch integrity and prevents accidental direct commits to protected environments.

What is the best way to extract architecture and task definitions from a GitHub issue?

Extract architecture and tasks by parsing the Modules section of a GitHub issue using the GitHub API. The Skill retrieves issue details and breaks down the module definitions into specific executable code commit tasks for sub-agent processing.

What happens if I try to execute GitHub issue tasks without a valid issue number or on an unsafe branch?

Executing GitHub issue tasks without a valid issue number or on an unsafe branch triggers built-in error handling. The Skill provides clear feedback regarding preconditions like branch safety and issue presence, halting execution until corrected.

Can I use sub-agent processing to handle specific task execution within an issue module?

Yes, sub-agent processing is used to handle specific tasks within an issue module. This allows the Skill to break down complex architectural changes from the GitHub issue into manageable, automated code commits handled by dedicated sub-agents.