Results for “changes”

Assesses Tanner stage to determine if physical changes of puberty have begun (stage G2/B2 or higher) for considering pubertal suppression. Triggered when a clinician evaluates pubertal development in an adolescent patient.

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

Assesses a patient’s ability to operate an insulin pump and make setting changes, evaluating dexterity, vision, mental health, and cognition for independent or assisted use. Triggered by phrases such as 'Check patient can manipulate pump controls' and 'Evaluate dexterity and vision for pump use'.

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

This skill directs lifelong treatment of cardiovascular risk factors, osteoporosis, and psychiatric symptoms in all patients with Cushing's syndrome until biochemical resolution of hypercortisolism. Use when managing any CS patient for long‑term comorbidity control; triggers include persistent hypertension, dyslipidemia, low bone density, depression, anxiety, or cognitive changes in the setting of known or suspected CS.

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

This skill guides annual evaluation of patients with primary adrenal insufficiency (PAI) for symptoms and signs of glucocorticoid and mineralocorticoid over- or under-replacement. Use during annual follow-up when assessing for weight changes, blood pressure abnormalities, edema, or symptoms such as fatigue, insomnia, or salt craving.

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

Execute a swarm plan wave by wave with filesystem isolation via git worktrees. For each wave, main context decides the scenario recipe + implementation contract for every task, then spawns one swarm-worker per task in parallel. Each worker executes its recipe and reports JSON status. Worktree merge-audit verifies write-set discipline before changes land on main. Aborts remaining waves on any audit or task failure.

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

Workflow Phase 8 (optional) — OWASP-aligned security review of pending code changes. Produces a prioritized findings report (Critical/High/Medium/Low) mapped to OWASP Top 10 and CWE IDs. Output at `docs/security/<slug>-<date>.md`. Read-only.

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

Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never commits, never touches consent paths. Disjoint from the commit skill (Phase 11 executor): the planner proposes a split; the executor lands one consented commit. Use when a working tree has accumulated heterogeneous changes that should not land as one commit.

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

Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.

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

Cross-consistency review of a drafted spec's diagrams. Verifies that C4 components appear in the dependency graph, class-diagram changes have matching DDL, every AC resolves to a concrete sequence, and the dependency graph is acyclic. Read-only. Run after `/spec-lint` passes and before implementation.

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

Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.

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

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

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

Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.

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

Build monitoring bots that poll APIs and send notifications on state changes (new listings, price alerts, status updates)

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

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

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

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.

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

Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.

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

Comprehensive REST API design review with automated linting, breaking-change detection, and design scorecards. Catches inconsistent conventions, missing versioning, and design smells before APIs ship. Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing API standards for a team.

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

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

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

Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.

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

Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.

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

Analyze Amazon product, sales, Amazon Ads, retail-readiness, and Best Seller Rank data to find commercially actionable growth opportunities. Use when Codex needs to identify which ASINs, campaigns, keywords, search terms, product targets, placements, categories, or BSR movements deserve more investment, optimization, harvesting, bid/budget changes, retail-readiness fixes, investigation, protection, or controlled scaling across Sponsored Products, Sponsored Brands, Sponsored Display, search term reports, targeting reports, campaign reports, placement reports, advertised/purchased product reports, Business Reports, organic performance, and BSR history.

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

Save, load, update, delete, merge, and navigate entity objects using TMS Aurelius ORM (TObjectManager). Use when the user asks how to persist or retrieve data with Aurelius, manage object lifetime, work with associations or collections at runtime, handle transactions, use cached updates, or control concurrency. Does NOT cover query DSL or criteria/projections (those are in a separate skill). Triggers on requests like "save an entity with Aurelius", "load a customer from the database", "add items to a collection", "how do I update an object", "flush changes", "delete a record with Aurelius", "merge a transient object", "how do transactions work in Aurelius", "batch updates Aurelius".

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

Verify that a requested bug fix changes observable behavior with a failing-before, passing-after reproduction and honest execution evidence.

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

Validate the gatOS mod against a new upstream Kitten Space Agency (KSA) game build — the break-check playbook run when the KSA game / its decompiled sources are bumped and you must decide whether gatOS needs changes. Covers exactly which gatOS surface couples to KSA and where, how to diff the CURRENT (new) vs PREVIOUS (old) decompiled sources, build-as-alarm, semantic-drift review, the reflection + render-internals coupling the compiler can't catch, and which docs to update in lockstep. Use when asked to "check gatOS against the new KSA build", "upgrade KSA", run the version-diff / break-check, or review a game update's impact. REQUIRES two KSA decompiled-source trees to be provided: CURRENT and PREVIOUS.

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