Agent Skills › serithemage/serverless-openclaw › solo-maintainer-inbox

solo-maintainer-inbox

GitHub

为独立维护者自动化处理PR和Issue。包括队列快照、变更检测、安全审查、分类标签及自动合并或关闭，旨在提升单人维护效率并确保代码质量与安全。

.agents/skills/solo-maintainer-inbox/SKILL.md serithemage/serverless-openclaw

触发场景

需要处理多个待审Pull Request 需要对Issue进行快速分类和清理

安装

npx skills add serithemage/serverless-openclaw --skill solo-maintainer-inbox -g -y

更多选项

非标准路径

npx skills add https://github.com/serithemage/serverless-openclaw/tree/main/.agents/skills/solo-maintainer-inbox -g -y

不安装直接使用

npx skills use serithemage/serverless-openclaw@solo-maintainer-inbox

指定 Agent (Claude Code)

npx skills add serithemage/serverless-openclaw --skill solo-maintainer-inbox -a claude-code -g -y

安装 repo 全部 skill

npx skills add serithemage/serverless-openclaw --all -g -y

预览 repo 内 skill

npx skills add serithemage/serverless-openclaw --list

SKILL.md

Frontmatter

{
    "name": "solo-maintainer-inbox",
    "description": "Triage issues and pull requests for a solo maintainer. Detect suspicious changes, validate safe PRs, label and comment when needed, and merge or close normal work automatically.",
    "argument-hint": "[optional focus, e.g. prs|issues|all]"
}

Solo Maintainer Inbox

Required Context

Read the shared policy first:

solo-maintainer-policy.md

PR Workflow

Snapshot the queue with gh pr list --state open.
For each PR, gather metadata with gh pr view --json and inspect changed files with gh pr diff --name-only.
Detect stacked PRs before merging. Merge ancestors first or mark superseded PRs clearly.
Apply the suspicious-change policy. If triggered, stop merge/release actions for that PR.
For safe PRs, run path-appropriate verification:
- docs-only: formatting or docs checks relevant to the changed files
- runtime, infra, or workflow changes: npm run build, npm run lint, npm run test, npm run test:e2e
Merge safe, green, mergeable PRs with a linear-history-friendly method such as gh pr merge --squash --delete-branch.

Issue Workflow

Snapshot the issue queue with gh issue list --state open.
Label and classify issues quickly: bug, docs, security, cost, ops, release blocker, or duplicate.
Request missing reproduction data only when the repository cannot infer it from context.
Close duplicates, obsolete reports, or already-fixed issues when evidence is clear.

Output Discipline

Leave short evidence for each merge, close, or stop decision.
When stopping for suspicious work, preserve changed files, failed checks, and the exact trigger from the shared policy.