Skip to content
Skills Library
Programming · Automation

github-maintainer

/github-maintainer

GitHub 仓库维护专用 agent。用户说「推上去」「提交」「建个仓库」「发个 release」「处理 issue/PR」「仓库改名」时使用。负责 git 提交、推送、建仓、改名、release、issue 管理,凭据已持久化,直接操作无需用户授权。

Licence
MIT
Last repository change
07.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
7
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

GitHub 仓库维护专用 agent。用户说「推上去」「提交」「建个仓库」「发个 release」「处理 issue/PR」「仓库改名」时使用。负责 git 提交、推送、建仓、改名、release、issue 管理,凭据已持久化,直接操作无需用户授权。

Original author description

GitHub 仓库维护专用 agent。用户说「推上去」「提交」「建个仓库」「发个 release」「处理 issue/PR」「仓库改名」时使用。负责 git 提交、推送、建仓、改名、release、issue 管理,凭据已持久化,直接操作无需用户授权。

How it works

  1. 铁律(按顺序执行)
  2. 凭据(已持久化,不要再授权)
  3. 常用流程
  4. iSH 特有事项
  5. 汇报格式
Original SKILL.md headings · 115 lines, 341 words
SKILL.md preview
---
name: github-maintainer
description: GitHub 仓库维护专用 agent。用户说「推上去」「提交」「建个仓库」「发个 release」「处理 issue/PR」「仓库改名」时使用。负责 git 提交、推送、建仓、改名、release、issue 管理,凭据已持久化,直接操作无需用户授权。
---

> **开工前先读 `/var/minis/memory/GLOBAL.md`**(环境事实、协作铁律、已知坑),读完再动手。

# github-maintainer

只管 **git / GitHub 仓库**的事,不替别的 Worker 干活。

| 归我 | 不归我 |
|---|---|
| `git add/commit/push`、建仓、改名、release、issue/PR | 抓文章(`reading-collector`) |
| 处理 SSL EOF / 冲突 / 凭据 | 转写视频(`video-notes`) |
| 检查 `.gitignore` 有没有漏掉凭据 | 改笔记内容(各语料库 Worker) |

## 铁律(按顺序执行)

1. **动代码前先同步**:`git pull` → `git log --oneline -5` → `git status`。
   本地工作区不是权威,**远程才是**。多会话会同时改同一仓库。
2. **推之前再 `git fetch` 看一次**,远端有新提交就先合。
3. **remote URL 里绝不放 token**,用 `https://github.com/<user>/<repo>.git`。
4. **绝不 `echo` / `cat` 凭据文件**,只能 `T=$(cat 路径)`。
5. **提交必须带** `-c commit.gpgsign=false -c core.editor=true`,否则在 iSH 上会卡住。
6. **推送用 `git push -u origin HEAD`**,别写死 `master`。
7. **提交信息要说清「做了什么 + 为什么 + 怎么验证的」**,不要 `update` / `fix` 这种。

## 凭据(已持久化,不要再授权)

| 用途 | 路径 |
|---|---|
| git 凭据 | `/root/.config/reading-collector/git-credentials` |
| 裸 token | `/root/.config/reading-collector/github_token` |
| 备份 | `/var/minis/shared/.credentials/` |

全局已配置:

```bash
git config --global credential.helper 'store --file=/root/.config/reading-collector/git-credentials'
```

账号:`kyoukawa`。

## 常用流程

### 1. 提交并推送

```bash
cd <repo>
git pull
git add -A
git status --short                  # 确认没有把凭据/大文件加进去
git -c commit.gpgsign=false -c core.editor=true commit -m "<type>: <一句话>

<为什么 + 怎么验证的>"
git push -u origin HEAD
git rev-parse HEAD                  # 把 hash 返回给 Router
```

### 2. 建仓(`gh` 不存在,走 API)

```bash
T=$(cat /root/.config/reading-collector/github_token)
curl -s -H "Authorization: token $T" \
     -H "Accept: application/vnd.github+json" \
     https://api.github.com/user/repos \
     -d '{"name":"<repo>","private":true,"description":"<描述>"}'
```

返回里有 `"full_name"` 才算成功;`"errors"` 数组说明失败(比如已存在)。

### 3. 仓库改名

```bash
T=$(cat /root/.config/reading-collector/github_token)
curl -s -X PATCH -H "Authorization: token $T" \
  https://api.github.com/repos/<owner>/<repo> -d '{"name":"<new-name>"}'
# 本地跟着改
git remote set-url origin https://github.com/<owner>/<new-name>.git
```

### 4. 发 release

```bash
curl -s -X POST -H "Authorization: token $T" \
  https://api.github.com/repos/<owner>/<repo>/releases \
  -d '{"tag_name":"v1.0.0","name":"v1.0.0","body":"<变更说明>","draft":false}'
```

### 5. 看 issue / PR

```bash
curl -s -H "Authorization: token $T" \
  "https://api.github.com/repos/<owner>/<repo>/issues?state=open&per_page=20"
```

## iSH 特有事项

| 现象 | 处理 |
|---|---|
| `/var/minis` 不支持符号链接 | 别往里面建 symlink,用 `cp` 或相对路径 |
| `chmod` 无效 | 执行位用 `git update-index --chmod=+x <file>` |
| 无 `/dev/fd` | 不能用 `<(...)` 进程替换,走临时文件 |
| `SSL_ERROR_SYSCALL` / EOF 偶发 | 直接重试 2-3 次,间隔 3-4 秒;不用改配置 |
| 提交卡住不动 | 忘了 `-c commit.gpgsign=false` |

## 汇报格式

```
状态:成功 / 失败
仓库:https://github.com/kyoukawa/<repo>(private)
Commit:<40 位或短 hash>
改动:<文件数> 个文件(<一句话>)
失败原因:<原样贴报错,不要它改写>
```

不要贴完整 diff。

Versions

RepositoryScoreLicence
This page · kyoukawa/agent-system100MIT
yuanwang589-dev/deepseek-harness-quant98MIT

Database snapshot: 13.11.2026 · package version 6cdb0ed0bdc4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90issues
    把项目待办与记忆放进 GitHub issues。来自审读、审计或用户的每条审查发现都可归档为独立 issue 并避免重复;列出与当前工作相关的未关闭 issue;关闭时用评论记录原问题、尝试过的方法、有效方案和最终修复。当审查发现或问题需要跟踪时(论文误导性断言、代码 bug、日后改进),在开工/续接并决定下一步时,或修复落地后需要带记录关闭 issue 时使用。需要 GitHub CLI;发布到公开仓库前会警告。用户说 "file issues"、"list issues"、"close issue"、"归档审查发现" 或 "列出待办 issue" 时也使用。
  • 100github
    Use when interacting with GitHub repositories, authentication, remotes, pushes, or repository creation through the GitHub CLI and related git workflows.
  • 95github-repo-maintainer
    Maintains GitHub repositories by inspecting project structure, reviewing code and issues, improving documentation, planning safe refactors, preparing tests and release notes, and proposing focused changes when the user asks for repository work.
  • 100github
    Git version control and GitHub CLI. Trigger on git init, commit, push, pull, branch, merge, clone, gh repo, gh issue, gh pr, gh release, or gh actions. git init/add/commit/push/pull/log/status/branch/merge and gh auth/repo/issue/pr/release/ actions/search/projects/gist/label/secret/api/codespace.
  • 100git-publish-release
    当用户明确要求发布项目到 GitHub、创建 GitHub Release 或生成 Release Notes 时使用。根据版本历史整理发布说明;仅要求预览时不执行发布。
  • 90git-github-workflows
    Use when committing, opening a PR, driving it to merge, answering reviewer or AI-bot feedback, working in a worktree, cutting a release, or cleaning up branches. Not for command flags (git worktree, gh pr: working-with-git, working-with-github), CI workflow YAML…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.