github-workflow

Enforce GitHub issue creation, progress updates, and agent attribution across feature workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RockwallJMC/piercedesk6 --skill github-workflow-rockwalljmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflow
Source: https://github.com/RockwallJMC/piercedesk6/tree/main/.claude/skills/github-workflow
Command: npx skills add https://github.com/RockwallJMC/piercedesk6 --skill github-workflow-rockwalljmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue and progress management for repo maintainers to ensure consistent issue creation, updates, and agent identification across cycles.

Core Features & Use Cases

  • Create and track GitHub issues for new features, bugs, and milestones; format progress updates; and link documentation with issues.
  • Enforce agent attribution on every interaction to maintain accountability and auditability.
  • Coordinate PR creation and linking to corresponding issues, plus final verification across tasks.

Quick Start

Open a new GitHub issue for a feature kickoff and begin posting phase updates with your agent name.

Frequently Asked Questions about github-workflow

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

FAQPage Schema
How do I enforce agent attribution and consistent metadata in GitHub issue tracking?

GitHub issue tracking requires strict agent name inclusion and frontmatter metadata on every interaction. This workflow enforces accountability by applying consistent templates to issue creation, phase updates, and pull request linking.

What is the best way to coordinate GitHub feature kickoffs and ongoing progress updates?

Coordinate GitHub feature workflows by opening issues for kickoffs and posting template-formatted progress updates. This ensures traceable updates across cycles, from initial feature creation through ongoing phase updates.

How do I link pull requests to corresponding GitHub issues for final verification?

Link pull requests to corresponding GitHub issues during PR creation to enable final verification across tasks. The workflow coordinates PR creation and linking while enforcing agent attribution for auditability.

Does this GitHub workflow management approach work without additional dependencies?

This GitHub workflow management approach operates without external dependencies. It relies entirely on consistent frontmatter metadata and issue comment templates to enforce agent identification and traceable updates.

Can I use standard GitHub issue templates for project management and milestone tracking?

Standard GitHub issue templates can be formatted for project management, tracking new features, bugs, and milestones. The workflow applies templates to issue comments and links documentation with issues for accountability.

Why does GitHub progress management fail without consistent agent identification?

GitHub progress management fails without agent identification because accountability and auditability are lost. Enforcing agent names on every interaction maintains consistent attribution across cycles and tasks.