github-workflows

Consolidates GitHub authentication, repository management, PR lifecycle, issues, and code review workflows.

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill github-workflows-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflows
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/github/github-workflows
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill github-workflows-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub work across separate auth, repo, PR, issue, and review workflows creates fragmented processes and missed steps. This Skill unifies the full GitHub operating loop into one explicit sequence from local repo state to merged code. ## Core Features & Use Cases - End-to-end PR lifecycle: Authenticate with gh, create topic branches, open PRs with safe --body-file handling, monitor checks, and merge with an explicit strategy. - Issue triage and code review: List, create, and label issues, then post structured review outcomes with critical/warning/suggestion severity buckets. - Multi-repo sync and reconciliation: Scan all local clones, compute ahead/behind counts, verify PR mergeability, and safely retire duplicate worktrees with verified git bundle backups. - Use Case: You inherit a machine with dozens of cloned repositories in unknown states. Use this Skill to inventory every repo, classify canonical versus duplicate clones, reconcile diverged branches, and verify remote SHA equality before any cleanup. ## Quick Start Use the github-workflows skill to authenticate with GitHub, open a PR for my current branch, and monitor its checks until merge.

Frequently Asked Questions about github-workflows

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

FAQPage Schema
How do I create a GitHub PR with a multiline Markdown description?

Write the PR body to a file and pass it with `gh pr create --body-file <path>` instead of a quoted `--body` argument. Double-quoted shell strings can execute backticks and `$()` substitutions, corrupting the description. Verify the result with `gh pr view --json body,url,state`.

How do I sync and reconcile multiple local git repositories?

Treat it as an inventory task: discover `.git` directories and files, deduplicate worktrees via `git rev-parse --git-common-dir`, fetch, then compute exact ahead/behind counts. Never infer merge needs from ancestry alone; compare patch IDs when squash merges are possible.

What should I check before committing to a public GitHub repository?

Verify `git config user.name` and `user.email` resolve to your GitHub account and noreply address, not a machine-local identity. Stage explicit paths, run `git diff --cached --check`, and scan the staged diff for secrets using bounded token patterns.

Does this workflow work when the gh CLI is unavailable?

Yes, it defines fallbacks using `GITHUB_TOKEN` from secure sources and direct `curl` calls to GitHub REST endpoints. Scope boundaries are preserved: issue endpoints, PR endpoints, and repo creation commands stay separate.

When should I not use this GitHub workflow skill?

Skip it for one-off `gh` commands, which should be run directly. It also does not apply to non-GitHub issue or review tasks, which belong to domain-specific skills for local code review, testing, or architecture work.