Skip to main content
在 Manus 中运行任何 Skill
一键导入
robdefeo
GitHub 创作者资料

robdefeo

按仓库查看 1 个 GitHub 仓库中的 7 个已收集 skills。

已收集 skills
7
仓库
1
更新
2026-06-20
仓库分布

Skills 分布在哪些仓库

按已收集 skill 数展示主要仓库,并显示它们在该创作者目录中的占比和职业覆盖。

仓库浏览

仓库与代表性 skills

scratchpad
软件开发工程师

Capture out-of-scope discoveries, ideas, tasks, and questions into a per-repo SCRATCHPAD.md while coding, then retrieve, archive, or promote them later. Use this skill whenever the user wants to write something down to deal with later instead of now — "park this", "note that", "jot this down", "add a note", "look at later", "I'll lose this otherwise". Route these here even when it looks like a trivial inline note — the point is durable, retrievable capture, not answering in the moment. Also use it to read items back ("what's open", "what did I park", "any notes about X"), tick them done, archive, or promote a parked item to a GitHub issue, memory, or project. And fire it yourself when, mid-task, you hit something outside the current scope — often unexpected behavior to work around but not fix now — that would otherwise be lost. This is for TRANSIENT, project-local capture; it is NOT durable memory (facts auto-loaded every session), reminders, meeting notes, PR text, or code comments.

2026-06-20
skill-scope
软件开发工程师

Decide how to scope a Claude skill before building or restructuring it: what belongs in one skill, what splits off, what merges, whether the work needs a new skill at all. Use BEFORE skill-creator whenever the user is (1) creating a new skill, (2) significantly restructuring or expanding an existing skill, (3) splitting one skill into two or merging two into one, or (4) unsure whether a workflow needs a new skill vs. extending an existing one. Skill-creator should not start scaffolding until skill-scope has run. Fires on: "create a skill", "make a skill", "new skill", "design a skill", "build a skill", "scope this skill", "should this be one skill or two", "is this skill too big", "is this skill too narrow", "where does this skill belong", "split this skill", "merge these skills", restructuring an existing skill, or `/skill-scope`. Skip for trivial edits where scope is settled (typos, trigger phrase tweaks, body rewording, packaging) — these don't reopen scope decisions.

2026-06-07
pr-address-feedback
软件开发工程师

Use this skill whenever the user wants to address, respond to, work through, or handle GitHub PR review comments — including code review feedback, reviewer suggestions, bot comments, or requested changes — even if they don't say "address". Handles the full end-to-end workflow: fetch threads, plan fixes, commit, push, and reply. Requires `gh` CLI.

2026-04-30
pr-create
软件开发工程师

Use this skill whenever the user wants to create, open, or raise a new GitHub pull request from the current branch — including phrasings like "open a PR", "raise a PR", "make a PR", "ship this". Drafts a Conventional Commits title and a Summary body that explains *why* and *what*, respects `.github/pull_request_template.md` when present, auto-links referenced issues, waits for approval, then pushes and opens the PR. Assumes commits already exist. Requires `gh` CLI.

2026-04-30
diataxis-documentation-guidance
技术写作员

Use this skill to classify, scope, split, draft, and review documentation with the Diataxis framework. Triggers include choosing tutorial/how-to/reference/explanation mode, resolving mixed-mode pages, rewriting docs into a target mode, and validating drafts with a checklist.

2026-03-06
para-second-brain
档案文员

Use this skill when the user wants to organize, classify, or maintain a PARA-method second brain. Triggers include asking where to file something, distinguishing projects from areas, processing an inbox, setting up a new project, completing or archiving a project, running a monthly review, validating system structure, or finding stale/orphaned content.

2026-02-19
amazon-working-backwards
项目管理专家

Guide the Amazon Working Backwards process from the 5 Questions through to a full PR-FAQ document. Use when the user wants to (1) draft answers to the Amazon 5 Questions for a proposal or idea, (2) refine or critique existing 5Q answers, (3) verify and challenge 5Q answers with probing questions, (4) generate a PR-FAQ document from 5Q answers, (5) review or critique an existing PR-FAQ against Amazon standards, or (6) clarify any element of the 5Q or PR-FAQ process. Triggers include mentions of "5 questions," "PR-FAQ," "PRFAQ," "working backwards," "press release FAQ," Amazon-style proposals, or requests to write/review product proposals in Amazon format.

2026-02-16
已展示 1 / 1 个仓库
已展示全部仓库