github-operations

Automates GitHub issue lifecycle and standardized comment posting workflows.

10|1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/maystudios/maxsimcli --skill github-operations-maystudios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/maystudios/maxsimcli/tree/main/templates/skills/github-operations
Command: npx skills add https://github.com/maystudios/maxsimcli --skill github-operations-maystudios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified GitHub interaction covering artifact types, comment conventions, CLI commands, and issue lifecycle. Used when reading from or writing to GitHub Issues, managing the project board, or posting structured comments.

Core Features & Use Cases

  • GitHub as Source of Truth: All project state lives on GitHub. No local .planning/ files. The canonical record for every phase, task, and progress update is an Issue or Issue comment on the configured repository.
  • Issue Structure: Phase issues, Task sub-issues, and nested relationships to represent plan and work breakdown.
  • Comment Types: Each posted artifact includes a type marker to indicate plan, research, context, progress, verification, or summary.
  • CLI Commands Reference: Provides a complete, router-based set of commands to manage issues, plan tasks, post comments, and update project boards.
  • Board Columns & Labels: Standardized workflow columns and labels guide issue progression and visibility.

Quick Start

Install MAXSIM and begin using the github-operations workflow to manage issues, tasks, and comments.

Frequently Asked Questions about github-operations

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

FAQPage Schema
How do I standardize GitHub issue lifecycles for automated workflows?

Standardize GitHub issue lifecycles by defining required markers, router-based CLI commands, and structured lifecycle steps for deterministic planning and execution. This ensures consistent issue progression and rollback capabilities across repository-wide coordination.

What are GitHub machine-readable comments and how do they work?

GitHub machine-readable comments include specific type markers indicating plan, research, context, progress, verification, or summary. These standardized markers categorize artifacts posted to issues, enabling clear workflow coordination and automated processing.

How to manage project board columns and labels for GitHub issue automation?

Manage project board columns and labels by using standardized workflow columns that guide issue progression and visibility. This standardizes the issue lifecycle process for phases, tasks, and nested relationships within the repository.

Can I use GitHub as the single source of truth without local planning files?

Yes, GitHub serves as the source of truth where all project state lives on GitHub Issues. No local .planning/ files are needed; the canonical record for every phase, task, and progress update is an Issue or Issue comment.

What CLI commands are needed to automate GitHub issue and task management?

Automating GitHub issue management requires a complete router-based set of CLI commands to manage issues, plan tasks, post structured comments, and update project boards, ensuring deterministic execution and rollback capabilities across the repository.

How do you structure nested GitHub issues for work breakdown and execution?

Structure nested GitHub issues by creating Phase issues, Task sub-issues, and nested relationships to represent plan and work breakdown. This hierarchy standardizes issue progression across project boards and review cycles.