菜单
Carry a config, pattern, or workflow from a sibling repository into this one. Use whenever a request references another local repo by relative path ("like ../calcipy", "see ../yak-shears/hk.pkl", "the way ../my-go-template does it"), or when migrating a project onto tooling another project already uses.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Write pull request review comments and replies to review threads in the user's voice. Use when reviewing a PR or diff and producing comments, when replying to a bot thread (CodeRabbit, Codex), when triaging or applying review findings, or when staging review feedback in a pr-<number>-review-comments.md file for the user to proofread before posting.
The user's full writing system for prose they author — README and docs text, landing copy, PR and commit descriptions, Linear proposals, design docs, Slack and email messages. Use when drafting or rewriting any human-facing prose, when a draft reads like AI wrote it, when stripping AI slop from documentation, or when relaying research output into a human-facing surface. CLAUDE.md carries the compressed rules; this carries the reasoning, the before/after pairs, and the per-format shapes.
incident.io assistant for working with incidents. View incident details, post updates to incident channels, interact with the incident agent, and query structured incident data. Use whenever the user mentions an incident ID (e.g., "INC-123"), asks about an incident, or uses the /incident command. Trigger proactively when you see an incident reference.
Freshens the repos listed in mani.yaml - syncs each with upstream, runs local gates, fixes CI on the default branch, and rolls template releases out to copier children. Arguments are a space-separated subset of repo names from mani.yaml; default is every repo.
On-demand UX critique for terminal UIs (Bubble Tea, Ratatui, Ink, Textual). Combines hyperskills:tui-design's layout/keybinding/color principles with impeccable's critique rigor (cognitive load, personas, heuristic scoring, P0-P3 severity), adapted for terminals — no CSS, no browser, no WCAG contrast math. Use when reviewing or critiquing a TUI's design, auditing keybinding discoverability, or checking terminal portability (NO_COLOR, monochrome degradation, multiplexer/SSH behavior).
Capture and persist browser screenshots or GIFs for visual review of a web UI. Use when verifying a UI change visually, reviewing a page's design or layout, recording a multi-step interaction (dropdown, hover, form flow), toggling dark mode for a comparison shot, or when a screenshot needs to be written to disk rather than only shown inline.
| name | port-from-sibling |
| description | Carry a config, pattern, or workflow from a sibling repository into this one. Use whenever a request references another local repo by relative path ("like ../calcipy", "see ../yak-shears/hk.pkl", "the way ../my-go-template does it"), or when migrating a project onto tooling another project already uses. |
The user keeps many small repos plus two copier templates (calcipy_template for
Python, my_go_template for Go) and propagates changes in both directions. The
reusable part of that work is the checklist, not the copying.
Read the reference in full. Not just the file named — its config, its lockfile pins, and any AGENTS.md, CLAUDE.md, or ADR that explains why it is shaped that way. Reading the file alone reproduces the shape and loses the reason.
Diff against local. State what already exists here, what conflicts, and what is genuinely missing. A migration usually turns out to be smaller than it looked.
Adapt, do not copy. The reference repo has a different name, language version, dependency set, and CI. Strip what is specific to it. A pasted config that names the wrong package is worse than none.
Note where the two have deliberately diverged. If local does something differently on purpose, say so and ask before overwriting it. Do not silently converge them.
Run it. The pre-commit hook, the lint step, the test suite — whatever the ported config claims to do. A config that evaluates is not a config that works.
The step most often forgotten. When the change is a general improvement rather than project-specific, it belongs in the template so every future project gets it:
../calcipy_template/package_template../my_go_template../app-template, with rendered output regenerated
under .ctt/Say explicitly whether the change should propagate upstream, and ask if it is not clear. Do not commit to the template repo without being asked.
Porting template to project is a copier update — use the copier-template
skill rather than hand-copying, so .copier-answers.yml stays truthful.
Porting project to template is manual, and needs the specifics generalized back
into {{ }} placeholders.
Porting project to project is the plain case this skill covers.