← 返回 Skills 市场
70
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install 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...
使用说明 (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 |
安全使用建议
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.'
功能分析
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.
能力评估
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.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install github-flow - 安装完成后，直接呼叫该 Skill 的名称或使用
/github-flow触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v0.1.0
Initial release: GitHub issue/PR workflow automation with plan-to-issue, structured PR creation, and code review topics
元数据
常见问题
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... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 70 次。
如何安装 GitHub Flow？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install github-flow」即可一键安装，无需额外配置。
GitHub Flow 是免费的吗？
是的，GitHub Flow 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
GitHub Flow 支持哪些平台？
GitHub Flow 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 GitHub Flow？
由 es6kr（@drumrobot）开发并维护，当前版本 v0.1.0。
推荐 Skills