원클릭으로 Manus에서 모든 스킬 실행

gh-workflow

스타0

포크0

업데이트2026년 7월 6일 13:58

GitHub workflows via the gh CLI — a collection of subskills for issues, pull requests, and wikis. Loads the right subskill on demand. Use when asked to create or open an issue, ticket, bug report, or decision/spike; open a pull request or submit changes for review; review a pull request or respond to review feedback; check CI / GitHub Actions status and diagnose a failing run; fetch, view, or pull up an issue by number or URL; triage, label, assign, close, or link existing issues; or generate and publish a GitHub Wiki (docs + architecture/Mermaid diagrams) for a repo.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

itisbryan

itisbryan/dear_bryan

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

gh-workflow

How I work with GitHub issues and pull requests through the gh CLI. This skill is an index — the actual guidance lives in focused subskills under references/, each loaded only when its topic comes up, so the base stays lean.

Prerequisites

GitHub CLI (gh) installed and authenticated (gh auth status). Run inside the target repository (or pass --repo owner/repo).

How to use

Match the request to the table below and load that subskill's file. Follow its guidance fully — a subskill is part of this skill, not a separate one, so don't announce a skill switch, just apply it.

Subskills

Trigger	Load	What it covers
Create/open an issue, ticket, bug report, or decision/spike ticket	`references/create-issues.md`	Structured issues with a Context / Problem / What to decide-do / References template, then `gh issue create`.
Open a pull request, submit changes for review	`references/create-pr.md`	Align with main, review the diff for out-of-scope concerns, draft a Summary/Changes/Testing/Notes PR, file follow-up issues.
Review a PR, approve/request changes, or respond to review feedback	`references/review-pr.md`	Read the diff + checks, post a verdict with batched inline comments, reply to threads on your own PR.
Check CI / Actions status, watch a build, diagnose why a run failed	`references/ci-triage.md`	`gh pr checks`/`gh run watch`; go to `--log-failed`, reproduce locally, re-run only transient failures.
Fetch, view, or pull up an issue by number or URL	`references/fetch-issue.md`	`gh issue view` with the right flags; scannable summary; resolve `#N` references.
Triage existing issues — label, assign, close, link, or branch off	`references/triage-issues.md`	`gh issue edit`/`close`/`develop`; reuse labels; close with a reason; safe bulk actions.
Generate/publish a GitHub Wiki, document a repo with architecture + Mermaid diagrams	`references/create-wiki.md`	Scan the repo, write Home/Architecture/module/diagram pages, publish to the native `.wiki.git`.

Rules for loading subskills

Load only when its trigger fires — progressive disclosure keeps the base skill small.
The subskills compose: create-pr files follow-ups with create-issues; create-issues can pull an existing ticket with fetch-issue. When a flow spans two, load both.

이 저장소의 다른 Skills

같은 저장소

parabol

itisbryan/dear_bryan

Draft and submit my daily standup to Parabol from my git activity, then submit only on my explicit OK. Uses the `paracli` CLI (brew install itisbryan/tap/paracli) for all the work; this skill just drives it interactively. Use when I say "do my standup", "submit my daily report", or "post my Parabol update".

2026-07-070

momentum

itisbryan/dear_bryan

Turn an overwhelming idea into one shippable slice and one next action — so you start today instead of drowning in the plan. Use when you have an idea you want to build but the scope/plan is overwhelming, when you're stuck at "where do I even start", when a project has stalled, or when you can feel burnout coming from a plan that keeps growing. The opposite of a big plan — it shrinks, it doesn't expand.

2026-07-060

redteam

itisbryan/dear_bryan

Authorized web-application penetration testing — recon, vulnerability analysis, proof-based exploitation, and a professional report. "No exploit, no report" — every finding needs reproducible evidence. Hard guardrails for authorization, scope, and secret-leakage. Use when asked to "pentest [URL]", "security-test this web app", "find vulns in [URL]", or "OWASP-test" a running application the user owns or is authorized to test.

2026-07-060

macos-app-design

itisbryan/dear_bryan

Guides distinctive, native-feeling macOS desktop app GUI design — recommends or lets you pick a Mac app archetype (system-native, pro/dense, content-first, menu-bar utility, prosumer-creative), then builds a real system of window chrome, materials, semantic colors, SF type, and native controls so the app reads as a real Mac app, not a web page in a window. Loads focused references (catalog, hig-structure, materials-color, typography, controls, motion-polish, anti-slop) on demand. Use when designing or restyling a macOS app UI in SwiftUI or AppKit, or when a Mac app "feels like Electron / like a website / not native."

2026-07-040

repo-study

itisbryan/dear_bryan

Study a specific public repo to learn how they solve a problem — clone it, trace the real mechanism through code and tests, mine git history for the why, and write an evidence-cited learnings doc with what to adopt. Use when asked to "learn from repo X", "how does project Y do Z", "study this codebase", "what can we steal from", or "write a doc on how they built" something.

2026-07-030

brainstorm

itisbryan/dear_bryan

Turn a rough idea into an approved design before any code — explore intent, constraints, and 2-3 approaches through one-question-at-a-time dialogue, then write a design doc the user signs off on. Use before creating a feature, component, or behavior change, especially when a task seems "too simple to need a design."

2026-07-020

name

gh-workflow

description

gh-workflow

Prerequisites

GitHub CLI (gh) installed and authenticated (gh auth status). Run inside the target repository (or pass --repo owner/repo).

How to use

Subskills

Trigger	Load	What it covers
Create/open an issue, ticket, bug report, or decision/spike ticket	`references/create-issues.md`	Structured issues with a Context / Problem / What to decide-do / References template, then `gh issue create`.
Open a pull request, submit changes for review	`references/create-pr.md`	Align with main, review the diff for out-of-scope concerns, draft a Summary/Changes/Testing/Notes PR, file follow-up issues.
Review a PR, approve/request changes, or respond to review feedback	`references/review-pr.md`	Read the diff + checks, post a verdict with batched inline comments, reply to threads on your own PR.
Check CI / Actions status, watch a build, diagnose why a run failed	`references/ci-triage.md`	`gh pr checks`/`gh run watch`; go to `--log-failed`, reproduce locally, re-run only transient failures.
Fetch, view, or pull up an issue by number or URL	`references/fetch-issue.md`	`gh issue view` with the right flags; scannable summary; resolve `#N` references.
Triage existing issues — label, assign, close, link, or branch off	`references/triage-issues.md`	`gh issue edit`/`close`/`develop`; reuse labels; close with a reason; safe bulk actions.
Generate/publish a GitHub Wiki, document a repo with architecture + Mermaid diagrams	`references/create-wiki.md`	Scan the repo, write Home/Architecture/module/diagram pages, publish to the native `.wiki.git`.

Rules for loading subskills

Load only when its trigger fires — progressive disclosure keeps the base skill small.
The subskills compose: create-pr files follow-ups with create-issues; create-issues can pull an existing ticket with fetch-issue. When a flow spans two, load both.