菜单
Rename or refactor a symbol safely by searching every naming-case variant across code, tests, docs, configs, and JSON. Use when renaming any identifier so no reference is missed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create a well-structured GitHub issue with duplicate detection, code verification, and auto-labeling. Use whenever the user asks to create, file, open, log, or raise a GitHub issue, in any wording.
Implement a GitHub issue step by step - ask about the branch, the PR target, and the phases first, then run the work and the review cycle with the review-pr skill. Use whenever the user asks to implement, work on, or execute a GitHub issue.
Review a GitHub pull request and post one clear review, with inline comments. The default is collaborative - you analyze deeply, explain the changes in simple terms, ask the user about each finding, and post a review that reflects their decisions. Use when the user asks to review a PR. --no-verdict = programmatic COMMENT-only mode that also writes .reviews/<PR_NUMBER>-review.md (used by implement-issue). --autonomous = unattended review that posts a formal verdict.
Shape git commits well - atomic one-concern commits, conventional-commit subjects, why-focused bodies, and a branch history that reads as a clear story. Use when composing commits.
Create a git branch from a base and set its upstream at once, so a later push can never land on the base branch. Use when starting work that needs its own branch.
Root-cause a bug or a failed fix with evidence, not guesses - brainstorm causes, research them in parallel, confirm one with logs before changing code. Use when a reported behavior needs root-causing or a fix attempt has failed.
| name | rename-symbol |
| description | Rename or refactor a symbol safely by searching every naming-case variant across code, tests, docs, configs, and JSON. Use when renaming any identifier so no reference is missed. |
When you rename or refactor any symbol, search all naming variants (camelCase, PascalCase, snake_case, kebab-case, UPPER_CASE) across the whole project (code, tests, docs, configs, and YAML/JSON), not just the obvious code references. A missed variant in a config key or a data file is the usual cause of a rename that runs fine but breaks at runtime.
Extra traps in this repo:
src/lib/*.js (with its *.test.js) and inline in src/full.liquid or src/middleware/calendar_weather_proxy.gs. Rename it in every copy and its test, and update the extracted-helper table in src/AGENTS.md. Renaming only src/lib leaves the live code calling the old name.keyname values in src/form_fields.yml and the custom_fields keys in .trmnlp.yml are read by TRMNL and by full.liquid (e.g. trmnl.plugin_settings.custom_fields_values.<keyname>). Renaming a key means renaming it in the template read, the form field, and the trmnlp sample data together.CONFIG keys and the ?src=... / URL parameter names (token, src, tz, lat, lon) are part of the polling-URL contract documented in MIDDLEWARE_SETUP.md and baked into the published recipe. Renaming one breaks live deployments; treat it as a contract change, not a local rename..../blob/master/... URLs in form_fields.yml point at real repo paths; renaming a file changes those URLs. Do not break them.