「stack」の検索結果

Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

日本語の概要は準備中です。原文の説明を表示しています。

Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

日本語の概要は準備中です。原文の説明を表示しています。

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch and summarize review comments from the active pull request

日本語の概要は準備中です。原文の説明を表示しています。

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

日本語の概要は準備中です。原文の説明を表示しています。

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work, and before telling the user that something was never recorded.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

日本語の概要は準備中です。原文の説明を表示しています。

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.

日本語の概要は準備中です。原文の説明を表示しています。

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

日本語の概要は準備中です。原文の説明を表示しています。

Find failing PR checks, inspect logs or external check links, and apply focused fixes

日本語の概要は準備中です。原文の説明を表示しています。

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

日本語の概要は準備中です。原文の説明を表示しています。

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when integrating a new requirement into an existing design.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.

日本語の概要は準備中です。原文の説明を表示しています。

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

日本語の概要は準備中です。原文の説明を表示しています。

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

日本語の概要は準備中です。原文の説明を表示しています。

Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.

日本語の概要は準備中です。原文の説明を表示しています。