メニュー
Use this skill when the user wants to audit code consistency issues — when the same problem is solved in different ways across the codebase. Activate on /realign.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | realign |
| description | Use this skill when the user wants to audit code consistency issues — when the same problem is solved in different ways across the codebase. Activate on /realign. |
Activate when the user invokes /realign.
The user provides two arguments:
"user group assignment", "volume migration", "error handling")Example: /realign src/services/payments "error handling"
Read the scope path. Use the hint to identify the specific pattern or operation the user noticed. Understand how the anchor implements it.
Search beyond the scope for every other place in the codebase that solves the same or related problem. The scope is where the user noticed it — not a fence around the search.
Look for two categories of inconsistency only:
fetch vs axios, declarative config vs imperative script)Do NOT flag:
Group findings by pattern. For each group:
[file:line](path#Lline) format so the user can jump to surrounding context in their editorExample group:
## Error handling in service calls
Found 3 different approaches:
**Try/catch with logger** — [src/services/payments/charge.ts:42](src/services/payments/charge.ts#L42)
\```ts
try {
await stripe.charge(amount);
} catch (err) {
logger.error(err);
throw err;
}
\```
**Result type** — [src/services/payments/refund.ts:18](src/services/payments/refund.ts#L18)
\```ts
const result = await safeCall(() => stripe.refund(chargeId));
if (!result.ok) return { error: result.error };
\```
**Unhandled** — [src/services/payments/webhook.ts](src/services/payments/webhook.ts)
(no error handling found around external call at line 31)
For each pattern group, propose a canonical form — the clearest, most explicit implementation found in the repo, or your own recommendation if none stands out. State your reasoning in one sentence.
Ask the user which groups they want to standardize and whether they agree with the proposed canonical. Continue conversationally from there — no menus or numbered choices.
Identify structural problems in a codebase and write them up as technical debt documentation — one file per issue in a subfolder, plus an index. Use this skill when the user asks about structural problems, code smells, maintainability issues, architectural concerns, god classes, tight coupling, or "what's wrong with this code at a high level." Also use it when the user says things like "what should we clean up", "where is this hard to change", "what are the pain points", or "document our tech debt." The skill produces actionable write-ups, not vague observations.
Release a new version of a plugin in this repo. Handles the full release workflow — bumps both plugin.json files, writes the changelog entry, updates the Skills or Agents section of the plugin README when something new was added, and runs the sync scripts. Invoke with /release or whenever the user says "bump version", "release plugin", "add changelog", "run sync", or asks to publish or version a plugin after making any kind of change.
Create or update .agents/OPERATOR.md in the current workspace — a personal profile that tells AI models who you are, your skill levels, and how you like to collaborate. Only invoke when the user explicitly runs /operator-setup. Do not auto-trigger based on context.
Use this skill for systematic scenario analysis — whenever a problem involves multiple variables, states, conditions, or failure modes and the user needs to enumerate the scenario space to find gaps, validate assumptions, or ensure coverage. Activate eagerly when the user asks "what cases should I handle?", "what could go wrong?", "am I missing any scenarios?", "how do I systematically test/model this?", or when they describe a decision table, state machine, input space, feature flag combination, risk matrix, or any artifact where multiple interacting variables might produce unexpected outcomes. Also use for non-testing contexts: config-flag interactions, requirement gap-finding, risk registers, design tradeoffs, business rule validation. This skill selects the right systematic technique, explains its reasoning, confirms with the user, and produces a structured markdown output for gap detection in code, requirements, design docs, or business rules.
Use this skill when the user wants to add test coverage targeting blind spots in a specific method — uncovered branches, edge cases, or unusual inputs. Activate on explicit requests to cover blind spots or when the user asks "what should I test here?" about a particular method. This is not about achieving 100% line coverage, but about ensuring the method behaves correctly in scenarios that are easy to miss.
Reference for adding and ordering Aspire deploy pipeline steps, tagging steps, parameterizing deployment with AddParameter, configuring per-environment values with WithEnvironment, and using PipelineStepContext services. Use when asked to add a pipeline step, order deploy steps, set up infrastructure provisioning, configure deployment, or wire up aspire deploy.