Results for “changes”

Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards.

The English summary is being prepared. Showing the original description.

Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.

The English summary is being prepared. Showing the original description.

Structured, risk-aware code review of a GitHub pull request using the gh CLI, with diff triage, unresolved-thread suppression, and severity-grouped findings ending in an approve/request-changes verdict.

The English summary is being prepared. Showing the original description.

Investigate and fix failing CI. Takes a PR reference, one or more CI run/job URLs, or freeform text describing where the failures are, then enumerates failing workflows/jobs/steps, determines the root cause (often one shared cause behind several red checks), proposes a fix plan, applies code changes, commits, pushes, watches the new runs, and repeats until checks pass. Use when the user says "fix CI", "CI is red", "checks are failing", "the build is broken on my PR", "fix the failing jobs", or pastes a failing CI run URL. Do NOT use for authoring new workflows, or for read-only diagnosis with no fix intent — use gha-log-reader for that.

The English summary is being prepared. Showing the original description.

Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").

The English summary is being prepared. Showing the original description.

Search the web and open-source code for library usage, API syntax, and documentation via Exa. Use this whenever verifying an API signature, looking up how a library is used, checking a config file format, or resolving an error from a third-party dependency -- including when you think you already know the answer, since library APIs drift. Also use for questions documentation cannot answer: release timing, breaking changes, "is X still maintained", licensing, security advisories, and ecosystem comparisons.

The English summary is being prepared. Showing the original description.

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

The English summary is being prepared. Showing the original description.

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"

The English summary is being prepared. Showing the original description.

Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.

The English summary is being prepared. Showing the original description.

Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.

The English summary is being prepared. Showing the original description.

Auto-commit changes after a Spec Kit command completes

The English summary is being prepared. Showing the original description.

Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.

The English summary is being prepared. Showing the original description.

Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.

The English summary is being prepared. Showing the original description.

Auto-commit changes after a Spec Kit command completes

The English summary is being prepared. Showing the original description.

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

The English summary is being prepared. Showing the original description.

Set up kpopper watch for background branch compatibility, scoped shared facts, and daily review. Use when asked to watch a project's graph, check worktree changes against main, share external observations, or install a kpopper routine. Ordinary followup capture recommends scheduling without enabling it.

The English summary is being prepared. Showing the original description.

[Workflow] Reconcile canonical specs, test cases, integration tests and docs after code changes, bug fixes or PR reviews; verify changed behavior.

The English summary is being prepared. Showing the original description.

[Utilities] Use when a workflow step or the user asks for an HTML session wrap-up: work, changes, rationale, how it works, stale docs and lessons.

The English summary is being prepared. Showing the original description.

[Workflow] Investigate and fix bugs, crashes or regressions at the root cause, with reviewed changes and regression tests that prove the fix.

The English summary is being prepared. Showing the original description.

[Process] Use when the active workflow has finished its steps or the user asks to close it: checks outcome evidence and owned changes, then closes the workflow; recovery state stays until an explicit /clear.

The English summary is being prepared. Showing the original description.

[Workflow] Author canonical specs from existing code, update them after changes, or audit staleness; reconcile behavior and test evidence.

The English summary is being prepared. Showing the original description.

[Code Quality] Use when a workflow step or the user asks for rationale evaluation or critical judgment of a decision, claim or statement: necessity, options, trade-offs. --validate-findings checks findings; --fix-loop fixes. Diffs: changes-review.

The English summary is being prepared. Showing the original description.

[Code Quality] Use when analyzing npm package upgrades, outdated dependencies or breaking changes and preparing a phased upgrade plan.

The English summary is being prepared. Showing the original description.

[Utilities] Use when a project adds, changes, lists or removes its OWN protocol rules layered over a framework skill (additive only). list | add | update | delete.

The English summary is being prepared. Showing the original description.