← Back to Skills Marketplace
drumrobot

GitHub Flow

by es6kr · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
70
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install github-flow
Description
GitHub issue and PR workflow automation. plan-to-issue - convert plan/research MD to GitHub issue body/comments [plan-to-issue.md], pr - create PR with struc...
README (SKILL.md)

GitHub Flow

Convert plans, research, and implementation results into GitHub issues and PRs.

Topics

Topic Description Guide
plan-to-issue Convert plan/research MD to GitHub issue body or comments plan-to-issue.md
pr Create PR with structured body, test plan, and optional visual attachments pr.md
review Review PR code and post structured review comments review.md

Applicability

This skill applies automatically when git remote get-url origin contains github.com. For non-GitHub remotes (GitLab, Bitbucket, etc.), this skill does not apply.

Core Rules

1. Verification Plan Required

Every issue body and PR body must include a verification/test plan section. This is shared with code-workflow's plan step.

2. No Internal Paths in Issues/PRs

.ralph/docs/, .ralph/fix_plan.md, .omc/ and other internal working paths must never appear in GitHub issue body, comments, or PR body. These are local-only artifacts.

Instead of: "See .ralph/docs/generated/plan-180.md" Write: The actual content inline, or "See the implementation plan comment below"

3. Body vs Comment Selection

Content Type Target Reason
Implementation plan (confirmed) Issue body update Stable reference for the issue
Checklist (impl/verify) Issue body update Trackable via GitHub checkbox
Discussion items / open questions Issue comment Threaded, time-stamped, doesn't clutter body
Progress updates Issue comment Chronological record
Review feedback summary Issue comment Preserves review history
Usage Guidance
This skill appears to actually perform GitHub actions (create/edit issues, create PRs, post review comments) using git and the GitHub CLI. Before installing: 1) Confirm you want the agent to run gh/git commands that can create or modify repo data. 2) Ensure the environment provides the gh CLI and git, and that authentication is handled safely (prefer a least-privilege GitHub token or an authenticated gh session). 3) Require the agent to ask for explicit confirmation before any write action (PR/issue creation or posting comments). 4) Test in a fork or non-production repo first. 5) If you expect the skill to be read-only or only provide templates, ask the maintainer to explicitly declare that and/or to list required binaries and credentials in the metadata. Providing those declarations would resolve the main incoherence and raise confidence toward 'benign.'
Capability Analysis
Type: OpenClaw Skill Name: github-flow Version: 0.1.0 The github-flow skill bundle provides structured automation for managing GitHub issues, pull requests, and code reviews using the 'gh' CLI and 'git'. The instructions in SKILL.md, plan-to-issue.md, and pr.md include explicit safety rules to sanitize internal environment paths (e.g., .ralph/, .omc/) before posting to GitHub and require user confirmation via AskUserQuestion before creating PRs. The logic is consistent with its stated purpose and lacks any indicators of malicious intent or unauthorized data exfiltration.
Capability Assessment
⚠ Purpose & Capability
The skill's stated purpose is GitHub issue/PR automation and its SKILL.md repeatedly instructs use of git and the GitHub CLI (gh) and performing authenticated actions (create/edit issues, create PRs, post comments). Yet the registry metadata lists no required binaries and no primary credential. A GitHub-integrated workflow would reasonably require git, gh, and some authenticated GitHub credential (gh auth or GITHUB_TOKEN). The absence of these declarations is inconsistent.
ℹ Instruction Scope
The SKILL.md, plan/pr/review docs instruct the agent to read plan files, construct sanitized bodies, run git/gh commands, write temporary files (e.g., /tmp/pr-review.md), and post to GitHub. All actions stay within the described domain (issues/PRs/reviews) and include explicit sanitization rules for internal paths. The instructions do not ask for unrelated system secrets or unrelated file paths, but they assume the ability to run git/gh and access the repo.
✓ Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk (nothing is written to disk by an installer).
⚠ Credentials
No environment variables or primary credential are declared, yet the workflow requires authenticated GitHub operations. This is disproportionate: either the skill should declare that it needs GH credentials (GH_TOKEN/GITHUB_TOKEN or rely on gh being logged in) and/or list git/gh binaries as requirements, or it should explicitly operate in read-only/template mode only. As written, it provides write-capable instructions without declaring necessary auth requirements.
✓ Persistence & Privilege
The skill does not request permanent inclusion (always: false) and does not modify other skills or system-wide agent settings. Autonomous invocation is allowed (default) but not combined with other high-risk flags.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install github-flow
  3. After installation, invoke the skill by name or use /github-flow
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release: GitHub issue/PR workflow automation with plan-to-issue, structured PR creation, and code review topics
Metadata
Slug github-flow
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is GitHub Flow?

GitHub issue and PR workflow automation. plan-to-issue - convert plan/research MD to GitHub issue body/comments [plan-to-issue.md], pr - create PR with struc... It is an AI Agent Skill for Claude Code / OpenClaw, with 70 downloads so far.

How do I install GitHub Flow?

Run "/install github-flow" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is GitHub Flow free?

Yes, GitHub Flow is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does GitHub Flow support?

GitHub Flow is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created GitHub Flow?

It is built and maintained by es6kr (@drumrobot); the current version is v0.1.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments