How do I install the Github Workflow skill?

Run npx skillmds@latest add tomevault-io/github-workflow-6 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Workflow by tomevault-io — Agent Skill

Name: Github Workflow
Author: tomevault-io

File contents

GitHub Workflow Skill

Guidance for managing the development workflow through GitHub.

Issue State Labels

Label	Description	When to Apply
`ready`	No blocking dependencies	Issue can be picked up
`in-progress`	Currently being implemented	Developer starts work
`blocked`	Waiting on dependencies	Has unresolved blockers
`needs-review`	PR open, awaiting reviews	PR created

gh issue edit {n} --add-label "in-progress" --remove-label "ready"
gh issue edit {n} --add-label "needs-review" --remove-label "in-progress"

Dependency Tracking

In issue body:

## Dependencies
Depends on #12 (User authentication)
Depends on #15 (Database schema)

Parse dependencies:

gh issue view {n} --json body --jq '.body' | grep -oE "Depends on #[0-9]+" | grep -oE "[0-9]+"
gh issue view {dep} --json state --jq '.state'

Agent Identification

All GitHub interactions must include an agent identifier header.

Format: **[Agent Name]** at the start of every issue body, PR description, and comment.

Standardized Review Comments

Since all agents share the same GitHub user, reviews use standardized comments:

Approval:

✅ APPROVED - [Role]
[Summary]

Changes Requested:

❌ CHANGES REQUESTED - [Role]
[Issues to address]

Required Reviews Per PR

Review	When Required
Architect	Always
Designer	If UI changes
Tester	Always

Review Templates

Architect

gh pr comment {n} --body "**[Architect]**

✅ APPROVED - Architect

Clean architecture. LGTM."

Designer

gh pr comment {n} --body "**[Designer]**

✅ APPROVED - Designer

UI looks good. Accessibility met."

# Or if not applicable:
gh pr comment {n} --body "**[Designer]** N/A - No UI changes."

Tester

gh pr comment {n} --body "**[Tester]**

✅ APPROVED - Tester

**Tests:** All passing
**Manual:** Completed

Ready for merge."

Product Owner (Merge)

gh pr comment {n} --body "**[Product Owner]**

All required reviews complete:
- ✅ Architect
- ✅ Tester

Proceeding with merge."

gh pr merge {n} --squash --delete-branch

PR Approval Verification

Before merge:

✅ APPROVED - Architect present
✅ APPROVED - Tester present
✅ APPROVED - Designer present (if UI)
No outstanding ❌ CHANGES REQUESTED
CI/tests passing

gh pr view {n} --comments  # Check for approval comments

Labels

Priority

Label	Description
`priority:high`	Work first
`priority:medium`	Normal
`priority:low`	Work last

Type

Label	Description
`feature`	New functionality
`bug`	Bug fix
`enhancement`	Improvement

Common Commands

# Issues
gh issue list --state open --label "ready"
gh issue view {n}
gh issue edit {n} --add-label "in-progress"

# PRs
gh pr create --title "..." --body "..."
gh pr view {n} --comments
gh pr merge {n} --squash --delete-branch

# Milestones
gh issue edit {n} --milestone "v1.0"

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: github-workflow-6description: Manages GitHub workflow including issues, PRs, labels, and reviews. Use when working with GitHub issues, creating PRs, or coordinating reviews.---# GitHub Workflow SkillGuidance for managing the development workflow through GitHub.## Issue State Labels| Label | Description | When to Apply ||-------|-------------|---------------|| `ready` | No blocking dependencies | Issue can be picked up || `in-progress` | Currently being implemented | Developer starts work || `blocked` | Waiting on dependencies | Has unresolved blockers || `needs-review` | PR open, awaiting reviews | PR created |```bashgh issue edit {n} --add-label "in-progress" --remove-label "ready"gh issue edit {n} --add-label "needs-review" --remove-label "in-progress"```## Dependency TrackingIn issue body:```markdown## DependenciesDepends on #12 (User authentication)Depends on #15 (Database schema)```Parse dependencies:```bashgh issue view {n} --json body --jq '.body' | grep -oE "Depends on #[0-9]+" | grep -oE "[0-9]+"gh issue view {dep} --json state --jq '.state'```## Agent Identification**All GitHub interactions must include an agent identifier header.**Format: `**[Agent Name]**` at the start of every issue body, PR description, and comment.## Standardized Review CommentsSince all agents share the same GitHub user, reviews use standardized comments:**Approval:**```✅ APPROVED - [Role][Summary]```**Changes Requested:**```❌ CHANGES REQUESTED - [Role][Issues to address]```## Required Reviews Per PR| Review | When Required ||--------|---------------|| Architect | Always || Designer | If UI changes || Tester | Always |## Review Templates### Architect```bashgh pr comment {n} --body "**[Architect]**✅ APPROVED - ArchitectClean architecture. LGTM."```### Designer```bashgh pr comment {n} --body "**[Designer]**✅ APPROVED - DesignerUI looks good. Accessibility met."# Or if not applicable:gh pr comment {n} --body "**[Designer]** N/A - No UI changes."```### Tester```bashgh pr comment {n} --body "**[Tester]**✅ APPROVED - Tester**Tests:** All passing**Manual:** CompletedReady for merge."```### Product Owner (Merge)```bashgh pr comment {n} --body "**[Product Owner]**All required reviews complete:- ✅ Architect- ✅ TesterProceeding with merge."gh pr merge {n} --squash --delete-branch```## PR Approval VerificationBefore merge:1. `✅ APPROVED - Architect` present2. `✅ APPROVED - Tester` present3. `✅ APPROVED - Designer` present (if UI)4. No outstanding `❌ CHANGES REQUESTED`5. CI/tests passing```bashgh pr view {n} --comments # Check for approval comments```## Labels### Priority| Label | Description ||-------|-------------|| `priority:high` | Work first || `priority:medium` | Normal || `priority:low` | Work last |### Type| Label | Description ||-------|-------------|| `feature` | New functionality || `bug` | Bug fix || `enhancement` | Improvement |## Common Commands```bash# Issuesgh issue list --state open --label "ready"gh issue view {n}gh issue edit {n} --add-label "in-progress"# PRsgh pr create --title "..." --body "..."gh pr view {n} --commentsgh pr merge {n} --squash --delete-branch# Milestonesgh issue edit {n} --milestone "v1.0"```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/shwilliamson) — claim your Tome and manage your conversions.

Frequently asked questions

Github Workflow