菜单
Goal-oriented repository maintenance and release-readiness work for yolop. Use when the user asks for maintenance, release prep, repo health review, dependency refreshes, knowledge/docs alignment, test gap review, or general cleanup without prescribing an exact sequence.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/everruns/yolop --skill maintenance命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Cut a new yolop release. Prepares the release PR, runs publish-readiness checks, monitors CI publish to crates.io and the everruns Homebrew tap. Use when the user asks to release, cut a version, publish, or ship to crates.io / brew.
View and change yolop's own configuration, default provider and model, per-provider API tokens and models, endpoint base URLs, attribution, harness capabilities, and named --profile overlays. Use when the user asks to configure yolop, set a default provider/model, store an API key, point at a custom endpoint, enable/disable capabilities, set up a profile, or asks "what is your config / what can you configure".
Built-in guide to using yolop, slash commands, keyboard shortcuts, CLI flags, tools, and session controls. Use when the user asks how yolop works, what commands or shortcuts are available, what yolop can do, or wants help using the terminal UI.
正在显示 SKILL.md
| name | maintenance |
| description | Goal-oriented repository maintenance and release-readiness work for yolop. Use when the user asks for maintenance, release prep, repo health review, dependency refreshes, knowledge/docs alignment, test gap review, or general cleanup without prescribing an exact sequence. |
| metadata | {"internal":true} |
| user-invocable | true |
Goal: leave the repo materially healthier and closer to release-ready, with evidence.
knowledge/specs/maintenance.md owns the success bar and the
rationale behind each surface. This skill owns how to work a pass.
surfaces.md holds the per-surface commands and heuristics —
open it for the surfaces your scope actually covers.
Use the scope the user gave; otherwise state the one you inferred before
starting. Typical scopes: release readiness, CI health on main, everruns-*
dependency refresh, knowledge or docs drift, feature-completeness drift across
CLI / TUI / knowledge / README / tests, test gaps, code simplification, security
hygiene, performance of recently changed code, binary size, AGENTS / skills /
command hygiene.
A red CI on main outranks every other scope — fix it first, or open an issue
and report the pass blocked. Otherwise go highest-signal first: recent
diffs, failing checks, stale knowledge, outdated everruns-* versions.
Prefer fixing over reporting. Fix what is small and local; for anything larger, write a crisp finding and defer it to a GitHub issue naming the problem and its user-visible impact — then put the issue number in the report. Skipping a surface is fine; skipping it silently is not.
Keep each change PR-sized and independently reviewable. Do not fold a simplification sweep into an unrelated fix. When a bug surfaces, prefer the failing test before the fix.
Validation matches the surfaces you touched — the
checks in AGENTS.md, plus a live-provider smoke through
Doppler when the pass touched runtime behavior. Do not declare release-ready
for surfaces you did not actually check.
main CI is red and out of reachIf the user asks to ship the result, hand off to /ship.