← Back to Skills Marketplace
markma84

GitHub Bug Report

by MarkMa84 · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ⚠ suspicious
91
Downloads
0
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install github-bug-report
Description
Submit bug reports to GitHub for OpenClaw issues. Use when: (1)发现了明确的bug并想提交给官方; (2)官方产品出现问题需要报障; (3)想查询现有issue状态; (4)需要跟进已提交issue的进展. Includes issue templat...
README (SKILL.md)

GitHub Bug Report

向 OpenClaw 官方仓库提交 bug report 的标准化流程。

核心原则

  • 提交前先搜索是否有人已经报过同样的问题,避免重复
  • 格式按官方建议:标题含版本号、步骤编号、预期 vs 实际结果分开
  • 提交后用 cron 建跟进提醒,三天后 bump 一次

Issue 提交标准格式

标题格式:[版本号] Bug简述

内容必须包含:

## Bug Description
(清晰描述问题)

## Steps to Reproduce
1. 第一步
2. 第二步
3. 第三步

## Expected Behavior
(预期应该怎样)

## Actual Behavior
(实际出了什么岔子)

## Environment
- OS / 版本
- OpenClaw 版本
- Node 版本
- Model(如果是模型相关)

## Additional Context
(如有日志、截图、配置 JSON,贴在这里)

快速提交流程

1. 提交新 issue

# 使用 scripts/submit_issue.py
python3 scripts/submit_issue.py --title "[v1.x.x] Bug标题" --body "内容"

2. 提交后立即建 cron 跟进

提交成功后,用 cron 建一个 3 天后的提醒:

{
  "name": "Bug跟进-#\x3Cissue号>",
  "schedule": { "kind": "cron", "expr": "0 10 * * *", "tz": "Asia/Shanghai" },
  "payload": {
    "kind": "agentTurn",
    "message": "检查 GitHub issue #\x3Cissue号> 是否有官方回复,如果没有,去 bump 一下(留言:Any update?)"
  },
  "sessionTarget": "isolated",
  "delivery": { "mode": "announce" }
}

3. 检查是否已有重复 issue

提交前先搜索:

curl -s "https://api.github.com/search/issues?q=checkpoint+orphan+repo:openclaw/openclaw" \
  -H "Authorization: token $GITHUB_TOKEN"

常用 GitHub API

操作 API
查 issue GET /repos/openclaw/openclaw/issues/\x3Cnumber>
搜 issue GET /search/issues?q=关键词+repo:openclaw/openclaw
建 issue POST /repos/openclaw/openclaw/issues
更新 issue PATCH /repos/openclaw/openclaw/issues/\x3Cnumber>
查 repo 信息 GET /repos/openclaw/openclaw

GitHub Token

当前 token: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

Header 格式:

Authorization: token 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
Accept: application/vnd.github+json
Content-Type: application/vnd.github+json

相关文件

  • 提交脚本:scripts/submit_issue.py
  • 快速参考:references/quick-ref.md
Usage Guidance
Do not install or use this skill as-is. The package contains a plaintext GitHub token that could be valid and would allow API access to the openclaw/openclaw repository. Ask the author to remove the embedded token and change the code to accept a GITHUB_TOKEN (or other secret) provided at runtime; if you've already exposed this token (e.g., pasted it elsewhere), rotate/revoke it in GitHub immediately and check the token's scopes. Also verify you want automated cron-based 'bump' behavior before enabling any follow-up automation to avoid unintended spamming.
Capability Analysis
Type: OpenClaw Skill Name: github-bug-report Version: 1.0.2 The skill bundle contains a hardcoded GitHub Personal Access Token (PAT) `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` within `SKILL.md`, `scripts/submit_issue.py`, and `references/quick-ref.md`. While the script logic is focused on legitimate GitHub Issue management (searching, creating, and updating issues), hardcoding credentials is a severe security vulnerability. Furthermore, `SKILL.md` instructs the agent to establish cron jobs for automated follow-ups; while this aligns with the stated purpose of tracking bug reports, it represents a high-risk persistence mechanism that could be easily repurposed for malicious intent.
Capability Assessment
Purpose & Capability
The declared purpose (creating/searching/updating GitHub issues for the openclaw/openclaw repo) matches the script and instructions. However, instead of asking for a runtime credential (e.g., GITHUB_TOKEN) or documenting how to supply one, the skill embeds a plaintext token directly in SKILL.md and scripts. Embedding credentials is not necessary to achieve the stated purpose and is an inappropriate design choice.
Instruction Scope
SKILL.md instructs the agent/user to call the GitHub API and to create cron reminders; those actions are within the stated scope. But the instructions repeatedly include a literal Authorization token value and example curl commands using it, which causes the agent to use that embedded secret. The cron follow-up behavior (automatic bump reminders) could cause automated spamming of issues if misused and should require explicit user consent/configuration.
Install Mechanism
There is no install spec (instruction-only plus a small Python script). Nothing is downloaded from remote URLs or written during install. This lowers supply-chain risk.
Credentials
The skill declares no required environment variables but contains a hard-coded token (ghp_...) in both SKILL.md and scripts. Proper, proportionate behavior would be to require a single GITHUB_TOKEN environment variable (or document use of a personal access token) and not ship a credential. The embedded token grants repository-scoped API access and is a clear overreach for distributed code/documentation.
Persistence & Privilege
always:false and autonomous invocation are default and acceptable. The only persistence-related action in the docs is creating cron reminders for follow-up; that is not inherently malicious but creates ongoing automated activity and should be opt-in and limited. The skill does not request system-wide config changes or modify other skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install github-bug-report
  3. After installation, invoke the skill by name or use /github-bug-report
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Simplified: removed public/ layer, skill now at .openclaw/skills/github-bug-report/
v1.0.1
Fixed: move to .openclaw/skills/public/ (shared skills location)
v1.0.0
Initial release: submit bug reports to OpenClaw GitHub with standard format, API scripts, and cron follow-up
Metadata
Slug github-bug-report
Version 1.0.2
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 3
Frequently Asked Questions

What is GitHub Bug Report?

Submit bug reports to GitHub for OpenClaw issues. Use when: (1)发现了明确的bug并想提交给官方; (2)官方产品出现问题需要报障; (3)想查询现有issue状态; (4)需要跟进已提交issue的进展. Includes issue templat... It is an AI Agent Skill for Claude Code / OpenClaw, with 91 downloads so far.

How do I install GitHub Bug Report?

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

Is GitHub Bug Report free?

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

Which platforms does GitHub Bug Report support?

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

Who created GitHub Bug Report?

It is built and maintained by MarkMa84 (@markma84); the current version is v1.0.2.

💬 Comments