← Back to Skills Marketplace

GitHub Development Standard

Name: GitHub Development Standard
Author: sonicbotman

by SonicBotMan · GitHub ↗ · v2.0.0 · MIT-0

cross-platform ✓ Security Clean

667

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install github-development-standard

Description

完整的 GitHub 项目开发标准流程 - 9步流程 + 4层验证 + 15项验收清单

README (SKILL.md)

GitHub Development Standard v2.0

用方法论驯服低端模型，让代码质量不再妥协

💡 核心价值

解决低端模型在代码开发中的常见问题：

❌ 过度修改（200+ 行，夹带重构）
❌ 无验证（直接说"修好了"）
❌ 夹带私货（顺便优化、重构）

📋 9 步开发流程

1. 读 issue → 2. 写任务卡 → 3. 确定基线
     ↓
4. 列改动点 → 5. 编码 → 6. 本地验证
     ↓
7. 看 diff → 8. 写发布说明 → 9. 复盘

✅ 8 条编码纪律

先复制旧代码，再局部替换
改函数前，先通读输入/输出/副作用
涉及数据结构变化时，先搜所有使用点
不要同时改逻辑和风格
不要在 bug fix 里做重构
不要修改未被需求要求的行为
不要在没有验证前说"修好了"
不要让 release note 超前于实际代码

🔍 4 层验证

# Layer 1: 语法验证
python3 -m py_compile scripts/xxx.py

# Layer 2: 导入验证
python3 -c "from scripts.xxx import ClassName"

# Layer 3: 行为验证
python3 test_fix.py

# Layer 4: 回归验证
python3 -m pytest tests/

📊 15 项验收清单

A. 需求一致性（3 项）

A1. 我能用一句话说清这次修复的目标
A2. 我知道这次"不打算修"的内容有哪些
A3. 代码改动与 issue 描述一致

B. 技术正确性（4 项）

B1. 我基于正确版本开始修改
B2. 我没有重写整个文件
B3. 数据结构变化已同步所有引用点
B4. 新逻辑不会破坏旧逻辑

C. 测试验证（4 项）

C1. 语法检查通过
C2. 导入检查通过
C3. 最小样例验证通过
C4. 回归测试通过

D. 发布质量（4 项）

D1. diff 大小与任务规模匹配
D2. release note 与实际代码一致
D3. 版本号、文档、注释已同步
D4. 我可以指出这次改动的风险点

🔧 GitHub CLI 使用

# 查看 Issue
gh issue view 53 --repo owner/repo

# 评论 Issue
gh issue comment 53 --repo owner/repo --body "修复说明..."

# 关闭 Issue
gh issue close 53 --repo owner/repo

📄 多文件修复注意事项

同步修改 - 修改 README.md 时，检查其他语言版本
工具验证 - 用 grep 等工具验证比人工更可靠
文档清理 - 先整合内容，再删除冗余文件

📊 效果对比

指标	使用前	使用后	提升
Bug 修复返工率	60%	5%	↓ 55%
平均改动量	200+ 行	15 行	↓ 185 行
夹带私货率	70%	0%	↓ 70%

💡 核心理念

先定义问题，再定义改法，再写代码，再做验证，最后才发布。

🔗 相关链接

GitHub: https://github.com/SonicBotMan/github-development-standard
ClawHub: https://clawhub.com/skills/github-development-standard

让代码质量不再妥协 💕

Usage Guidance

This is a guidance/checklist skill — it doesn't contain code or ask for secrets. Before using: (1) review the linked GitHub repo if you want to trust the origin; (2) understand that examples call local commands (python, pytest, gh) and assume you run them in the target repository — they won't run by themselves; (3) the gh CLI requires authentication, but the skill doesn't request tokens — do not paste tokens or secrets into chat. If you allow an autonomous agent to act, be aware it could execute similar commands on your filesystem or against repositories it can access, so ensure it's pointed at the intended repo and that no sensitive data is present.

Capability Analysis

Type: OpenClaw Skill Name: github-development-standard Version: 2.0.0 The skill bundle defines a structured methodology and checklist for GitHub development workflows, aiming to improve AI code quality through rigorous verification steps. It utilizes standard development tools and commands (e.g., pytest, py_compile, and the GitHub CLI) for legitimate purposes and contains no evidence of malicious intent, data exfiltration, or harmful instructions in Skill.md.

Capability Assessment

✓ Purpose & Capability

The skill is a GitHub development standard (checklist and workflow). The SKILL.md content (9-step workflow, validation layers, checklist, and gh CLI examples) directly matches the name and description; there are no unrelated requirements or unexpected capabilities declared.

ℹ Instruction Scope

Instructions are focused on code-change discipline: reading issues, small diffs, syntax/import/tests, and using GitHub CLI for issue operations. They reference running python compile/import/tests and gh commands against a repo. This is appropriate, but the examples assume access to the project files and an authenticated gh CLI; the skill does not attempt to read unrelated system paths or exfiltrate data.

✓ Install Mechanism

No install spec and no code files; the skill is instruction-only, which minimizes installation risk. It does include example commands that rely on existing tools (python, pytest, gh), but it does not install anything itself.

ℹ Credentials

The skill declares no required environment variables or credentials, which is reasonable for a guidance document. However, using the gh CLI in practice requires authentication (gh auth) or credential material outside the skill; the skill does not request or handle secrets itself. There are no disproportionate or unexplained credential requests in the skill bundle.

✓ Persistence & Privilege

always is false and there are no install hooks or requests to modify other skills or system-wide settings. The skill does not request persistent presence or elevated privileges.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install github-development-standard
After installation, invoke the skill by name or use /github-development-standard
Provide required inputs per the skill's parameter spec and get structured output

Version History

v2.0.0

v2.0 精简版 - 9步流程 + 4层验证 + 15项验收清单 + GitHub CLI使用 + 多文件修复指南

v1.0.1

v1.0.1 - 符合 OpenClaw 规范的 Skill 包（含 YAML 元数据 + 完整文档 + 模板 + 示例）

v1.0.0

v1.0.0 初始版本：完整的 9 步开发流程 + 4 层验证体系 + 15 项验收清单 + 8 条编码纪律

Metadata

Slug github-development-standard

Version 2.0.0

License MIT-0

All-time Installs 2

Active Installs 1

Total Versions 3

Frequently Asked Questions

What is GitHub Development Standard?

完整的 GitHub 项目开发标准流程 - 9步流程 + 4层验证 + 15项验收清单. It is an AI Agent Skill for Claude Code / OpenClaw, with 667 downloads so far.

How do I install GitHub Development Standard?

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

Is GitHub Development Standard free?

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

Which platforms does GitHub Development Standard support?

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

Who created GitHub Development Standard?

It is built and maintained by SonicBotMan (@sonicbotman); the current version is v2.0.0.

More Skills