一键在 Manus 中运行任何 Skill

开始使用

cc-review

星标2

分支0

更新时间2026年7月6日 06:04

Run the cc-staff-reviewer over my Claude Code setup (user + project scope)

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

jmanuelrosa

jmanuelrosa/dotfiles

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

SKILL.md

readonly

name	cc-review
description	Run the cc-staff-reviewer over my Claude Code setup (user + project scope)
disable-model-invocation	true

Maintenance review of my Claude Code configuration.

Check for /insights data in ~/.claude/usage-data/ (facets/*.json preferred, else report.html). If neither exists, tell me to run /insights first, but offer to proceed config-only.
Use the cc-staff-reviewer subagent to review my setup at BOTH scopes: user (~/.claude) and the current project (.claude/ found from cwd). State which scope it actually detected.
Return its prioritized P0-P2 report, the adoption opportunities, the proposed new artifacts, the action table, and the top-3 next moves verbatim.
If the report lists adoption opportunities or proposed new artifacts, ask me which to take with AskUserQuestion (multiSelect; one option per item, description = the why + how in one line). Skip the question entirely when there are none.
Act on each accepted item here in the main conversation: config changes directly (settings.json, frontmatter, rule files); new skills via /skill-writer; settings/hooks via the update-config skill. Show what changed. If a changed file is a symlink into my dotfiles repo, say so and offer /commit there (new locally authored artifacts belong in that repo's registries). Drop declined items without ceremony.

The subagent never modifies files. In this conversation, modify files only for items I explicitly accepted in step 4.

同仓库更多 Skills

同仓库

agent-audit

jmanuelrosa/dotfiles

Audit Claude Code agent definitions for craft quality: delegation triggers, tool and model fit, context economy, reliability contracts. Reviews the agent .md files themselves, not the overall setup.

2026-07-062

coderabbit

jmanuelrosa/dotfiles

Walk open CodeRabbit review threads on a GitHub PR, investigate each in the code, then either fix it or reply to @coderabbitai explaining why it stays. Resolves each thread it handles. Stops before commit.

2026-07-062

jira

jmanuelrosa/dotfiles

Interact with Jira via acli. Create, update, view, transition, and comment on issues. Defaults to the SER project and produces descriptions that both product and engineering can follow, in proper ADF (Atlassian Document Format).

2026-07-062

jmanuelrosa/dotfiles

Generate the PR description from the current branch and open the PR (GitHub) or MR (GitLab), returning the URL

2026-07-062

skill-scout

jmanuelrosa/dotfiles

Recommend which skills from the catalog to add to the current project, matched to its tech stack and needs. Use when the user asks which skills to add, wants skills recommended for this repo or codebase, is discovering relevant skills, or is setting up a project. Excludes skills already installed globally and dependency-only skills.

2026-07-062

commit

jmanuelrosa/dotfiles

Stage changes, split the diff into atomic concerns when it makes sense, and write one strict conventional commit per concern. Stops at commit; does not push.

2026-07-062

name	cc-review
description	Run the cc-staff-reviewer over my Claude Code setup (user + project scope)
disable-model-invocation	true

Maintenance review of my Claude Code configuration.

Check for /insights data in ~/.claude/usage-data/ (facets/*.json preferred, else report.html). If neither exists, tell me to run /insights first, but offer to proceed config-only.
Use the cc-staff-reviewer subagent to review my setup at BOTH scopes: user (~/.claude) and the current project (.claude/ found from cwd). State which scope it actually detected.
Return its prioritized P0-P2 report, the adoption opportunities, the proposed new artifacts, the action table, and the top-3 next moves verbatim.
If the report lists adoption opportunities or proposed new artifacts, ask me which to take with AskUserQuestion (multiSelect; one option per item, description = the why + how in one line). Skip the question entirely when there are none.
Act on each accepted item here in the main conversation: config changes directly (settings.json, frontmatter, rule files); new skills via /skill-writer; settings/hooks via the update-config skill. Show what changed. If a changed file is a symlink into my dotfiles repo, say so and offer /commit there (new locally authored artifacts belong in that repo's registries). Drop declined items without ceremony.

The subagent never modifies files. In this conversation, modify files only for items I explicitly accepted in step 4.