GitHub Project Management

VerifiedSafe

GitHub project management for Bluegrass Songbook. Use when working with issues, milestones, labels, PRs, or release workflows.

Sby Skills Guide Bot
ProductivityIntermediate
7/22/2026
Claude CodeCursorWindsurfCopilotCodex
#github#issue-tracking#milestones#release-management#gh-cli

Recommended for

Automated summary

This skill covers GitHub project management for the Bluegrass Songbook repository using the gh CLI: issues, milestones, labels, pull requests, and release publishing.

Strengths

  • Supplies copy-paste gh commands to list, label, assign, and close issues
  • Documents the project's milestone table (2 through 10) plus how to create milestones and report open/closed progress
  • Explains the label pairings (song-submission + approved, song-correction + approved) that trigger GitHub Actions workflows
  • Includes bulk-operation patterns and a full tagged release creation example

Limitations

  • Tightly coupled to the Jollyhrothgar/Bluegrass-Songbook repo: labels, milestones, and workflows need rework for any other project
  • The provided content cuts off mid-way through the Pull Requests section, so the PR guidance is incomplete
  • Assumes gh is installed and authenticated without covering initial setup
When to use it

Reach for it when triaging issues, attaching them to milestones, applying labels, or preparing a release on the Bluegrass Songbook repository.

When not to use it

Avoid it on a different repository or before gh authentication is configured, since the milestone numbers and labels are specific to this project.

Security analysis

Safe
Quality score85/100

The skill is a reference guide for routine GitHub CLI operations (issues, milestones, labels, PRs, releases) against a specific repository. It uses powerful tools (gh, git tag/push, gh release create) but only for legitimate project management, with no destructive filesystem commands, no credential/secret exfiltration, no remote code fetching (curl|sh), no obfuscated payloads, and no attempts to disable safety controls. The only mildly risky item is the bulk-close pattern, which is label-scoped and recoverable.

Findings
  • •Bulk operation `gh issue list --label wontfix ... | xargs gh issue close` can mass-close issues if the label is misused, though it is scoped and not destructive to data.
How this analysis is made

Examples

Triage a new issue
Look at issue #57 in Jollyhrothgar/Bluegrass-Songbook, add the right label, and assign it to the List Management Tools milestone.
Milestone progress report
Give me the open and closed issue counts for every milestone in the Bluegrass Songbook repo.
Cut a release
Tag v1.2.0 and create a GitHub release for Bluegrass-Songbook titled 'v1.2.0 - Improve Search & Filtering' with notes summarizing the search changes.

name: github-project description: GitHub project management for Bluegrass Songbook. Use when working with issues, milestones, labels, PRs, or release workflows.

GitHub Project Management

Repository: Jollyhrothgar/Bluegrass-Songbook

Quick Reference

# Issues
gh issue list                           # Open issues
gh issue list --state all               # All issues
gh issue list --milestone "Name"        # By milestone
gh issue list --label bug               # By label
gh issue view 42                        # View issue details
gh issue close 42 -c "Fixed in abc123"  # Close with comment

# Milestones
gh api repos/:owner/:repo/milestones    # List milestones
gh api repos/:owner/:repo/milestones --jq '.[] | {number, title, open_issues}'

# Assign issue to milestone
gh api repos/:owner/:repo/issues/42 -X PATCH -F milestone=2

# Remove from milestone
gh api repos/:owner/:repo/issues/42 -X PATCH -F milestone=null

# Labels
gh issue edit 42 --add-label "bug"
gh issue edit 42 --remove-label "bug"

Milestones

| # | Title | Purpose | |---|-------|---------| | 2 | List Management Tools | User lists, setlists, offline access | | 3 | Improve Search & Filtering | Search features, filters, tagging | | 4 | Backlog | Lower priority items | | 5 | Fun Features | Leaderboards, easter eggs | | 6 | Content | New song sources, imports | | 7 | Playback Engine | Metronome, chord backing (future) | | 8 | Fiddle Tunes | ABC notation support (future) | | 9 | Tablature | Tab generation (future) | | 10 | Community | Profiles, contributions (future) |

Create a Milestone

gh api repos/:owner/:repo/milestones -X POST \
  -f title="Milestone Name" \
  -f description="What this milestone covers" \
  -f due_on="2025-03-01T00:00:00Z"  # Optional

Milestone Progress

# Get open/closed counts
gh api repos/:owner/:repo/milestones --jq '.[] | "\(.title): \(.open_issues) open, \(.closed_issues) closed"'

Labels

| Label | Purpose | |-------|---------| | bug | Something isn't working | | feature-request | Add something new that doesn't exist | | technical-debt | Non-blocking cleanup or improvements | | song-submission | New song variant or addition | | song-correction | Fix to existing song | | approved | Triggers GitHub Actions workflows | | new-data-source | New song collection to import | | rfc | Request for Comments - architectural decisions |

Automated Workflows

These label combinations trigger GitHub Actions:

| Labels | Action | |--------|--------| | song-submission + approved | process-song-submission.yml - adds new song | | song-correction + approved | process-song-correction.yml - updates song |

Common Workflows

Triage New Issue

# 1. View the issue
gh issue view 42

# 2. Add appropriate label
gh issue edit 42 --add-label "feature-request"

# 3. Assign to milestone
gh api repos/:owner/:repo/issues/42 -X PATCH -F milestone=2

# 4. Optionally add comment
gh issue comment 42 -b "Added to List Management milestone. Will address in next sprint."

Close Resolved Issue

# Close with reference to fix
gh issue close 42 -c "Fixed in commit abc123 / PR #45"

Bulk Operations

# Close all issues with a label
gh issue list --label "wontfix" --json number --jq '.[].number' | xargs -I {} gh issue close {}

# Add label to multiple issues
for i in 10 11 12; do gh issue edit $i --add-label "bug"; done

# Move issues to milestone
for i in 31 39 40; do gh api repos/:owner/:repo/issues/$i -X PATCH -F milestone=2; done

Create Release

# Tag and create release
git tag -a v1.0.0 -m "Version 1.0.0"
git push origin v1.0.0

gh release create v1.0.0 \
  --title "v1.0.0 - List Management" \
  --notes "## Features
- Drag-and-drop setlists
- Offline list access
- Full screen performance mode"

Pull Requests

# Create PR
gh pr create --title "Add setlist navigation" \
  --body "Closes #40" \
  --base main

# View PR checks
gh pr checks 45

# Merge PR
gh pr merge 45 --squash --delete-branch

# View PR comments
gh api repos/:owner/:repo/pulls/45/comments

Issue Templates

Issues are created via the web UI or:

gh issue create --title "Bug: description" \
  --body "## Steps to reproduce
1.
2.

## Expected behavior

## Actual behavior" \
  --label "bug"

Queries

# Issues without milestone
gh issue list --json number,title,milestone --jq '.[] | select(.milestone == null) | "\(.number): \(.title)"'

# Issues by author
gh issue list --author pixiefarm

# Recently updated
gh issue list --json number,title,updatedAt --jq 'sort_by(.updatedAt) | reverse | .[:5] | .[] | "\(.number): \(.title)"'

# Search issue content
gh issue list --search "offline in:body"

Project Board (if using GitHub Projects)

# List projects
gh api repos/:owner/:repo/projects

# Note: GitHub Projects v2 uses GraphQL - see gh project commands
gh project list
gh project view 1

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/github-project-management-mrwak9tc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/github-project-management-mrwak9tc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-project-management-mrwak9tc/download' --output '.skill-downloads/github-project-management-mrwak9tc/SKILL.md.part' && mv '.skill-downloads/github-project-management-mrwak9tc/SKILL.md.part' '.skill-downloads/github-project-management-mrwak9tc/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Quick Reference
# Issues
gh issue list                           # Open issues
gh issue list --state all               # All issues
gh issue list --milestone "Name"        # By milestone
gh issue list --label bug               # By label
gh issue view 42                        # View issue details
gh issue close 42 -c "Fixed in abc123"  # Close with comment

# Milestones
gh api repos/:owner/:repo/milestones    # List milestones
gh api repos/:owner/:repo/milestones --jq '.[] | {number, title, open_issues}'

# Assign issue to milestone
gh api repos/:owner/:repo/issues/42 -X PATCH -F milestone=2

# Remove from milestone
gh api repos/:owner/:repo/issues/42 -X PATCH -F milestone=null

# Labels
gh issue edit 42 --add-label "bug"
gh issue edit 42 --remove-label "bug"

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/github-project-management-mrwak9tc/SKILL.md' && test -s '.skill-downloads/github-project-management-mrwak9tc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/github-project' && cp -R '.skill-downloads/github-project-management-mrwak9tc' '.claude/skills/github-project'

Cursor
test -f '.skill-downloads/github-project-management-mrwak9tc/SKILL.md' && test -s '.skill-downloads/github-project-management-mrwak9tc/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/github-project' && cp -R '.skill-downloads/github-project-management-mrwak9tc' '.cursor/skills/github-project'

Codex
test -f '.skill-downloads/github-project-management-mrwak9tc/SKILL.md' && test -s '.skill-downloads/github-project-management-mrwak9tc/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/github-project' && cp -R '.skill-downloads/github-project-management-mrwak9tc' '.agents/skills/github-project'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/github-project-management-mrwak9tc'

openskills read 'github-project-management-mrwak9tc'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/github-project-management-mrwak9tc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills