Skip to main content
在 Manus 中运行任何 Skill
一键导入
GitHub 仓库

stage-cli

stage-cli 收录了来自 ReviewStage 的 9 个 skills,并提供仓库级职业覆盖和站内 skill 详情页。

已收集 skills
9
Stars
246
更新
2026-06-08
Forks
20
职业覆盖
3 个职业分类 · 已分类 100%
仓库浏览

这个仓库中的 skills

stage-chapters
软件质量保证分析师与测试员

Generate Stage chapters for the current local git branch and open them in a browser for review.

2026-06-08
deslop-ui
网页与数字界面设计师

Use when building or reviewing UI components, pages, or layouts to ensure premium, intentional design that never looks vibe coded

2026-05-05
fixing-ci
软件开发工程师

Use when CI is failing on a branch and you need to diagnose failures from GitHub, fix them locally with iterative verification, and re-push clean commits.

2026-05-05
fixing-pr-comments
软件质量保证分析师与测试员

Use when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback

2026-05-05
iterate-pr
软件开发工程师

Use when a PR is open and the user wants to autonomously monitor and fix PR review comments, CI failures, and rebase conflicts on a recurring loop, or when asked to babysit/iterate on a PR

2026-05-05
linear-issue
软件开发工程师

Use when creating a Linear issue from the current coding context, or when the user invokes /linear-issue. Infers team, priority, status, and relationships from conversation context, working directory, and git branch.

2026-05-05
quality-review
软件质量保证分析师与测试员

Use when reviewing code changes against AGENTS.md implementation quality standards, or when asked to do an implementation quality review

2026-05-05
rebase-origin-main
软件开发工程师

Use when rebasing the current branch onto origin/main, including resolving merge conflicts along the way

2026-05-05
trade-off
软件开发工程师

Use at any stage — planning, before implementing, or reviewing code that's already written — to surface high-level trade-offs that could significantly simplify the work. Scans two layers in strict priority order. First, user-facing behavior (features, flows, states, settings, notifications, undo, real-time, bulk ops) — cutting a behavior removes the architecture and code behind it. Second, architectural design (queues, caches, background jobs, new packages, new tables, new services, streaming, real-time infra) — cutting an architectural piece removes whole categories of implementation. Stops there; code-level simplification is outside scope. Proactively invoke whenever the scope of a task looks like it could grow, whenever you catch yourself about to add a queue, cache, new package, new table, new service, or behavior that wasn't explicitly requested, or when looking back at a recent diff that feels larger than the task warranted.

2026-05-05