「change」の検索結果

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

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

Autonomous iterative experimentation loop for any programming task. Guides the user through defining goals, measurable metrics, and scope constraints, then runs an autonomous loop of code changes, testing, measuring, and keeping/discarding results. Inspired by Karpathy's autoresearch. USE FOR: autonomous improvement, iterative optimization, experiment loop, auto research, performance tuning, automated experimentation, hill climbing, try things automatically, optimize code, run experiments, autonomous coding loop. DO NOT USE FOR: one-shot tasks, simple bug fixes, code review, or tasks without a measurable metric.

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

Adopt a virtual Chameleon exotic animal at animalhouse.ai. Adapts appearance to mood. Visual feedback on stat changes. Feeding every 6 hours. Uncommon tier animal.

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

Give Hermes phone capabilities without core tool changes. Provision and persist a Twilio number, send and receive SMS/MMS, make direct calls, and place AI-driven outbound calls through Bland.ai or Vapi.

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

Use when (1) building an AI agent that needs to communicate with other agents over the Agent2Agent (A2A) protocol, (2) publishing an AgentCard for discovery, (3) acting as an A2A client or server, or (4) integrating A2A capabilities into an existing agent framework. Solves agent isolation — enabling discovery, capability negotiation, task delegation, and structured data exchange across different frameworks and vendors.

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

Parallel 3-agent cleanup of recent code changes.

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

Operating discipline distilled from Claude Fable 5 for sessions and subagents on weaker models (Opus 4.x, Sonnet 5/4.x, Haiku 4.5) doing agentic coding. Load it at the START of any non-trivial task when not running on Fable 5: debugging, refactoring, changes across 2+ files, or unfamiliar code; and instruct a subagent on Opus/Sonnet/Haiku to read this skill with a non-trivial assignment. Triggers include "think like Fable", "fable-mode", "turn on discipline", "work carefully", dispatching a subagent on a weaker model, and repeated mistakes or rework in the session. NOT needed for trivial edits (rename, typo, one-liner) or purely conversational answers.

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

Analyze a failing test or design the right test coverage for a change

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

Implement a scoped feature or change with minimal, direct execution steps

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

Run quality gates, commit, push, and open a PR with the canonical template. Use when the user runs /ship or wants to ship the current changes.

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

Create a Beads-first refactor plan through detailed interview, repo verification, alternatives, scope boundaries, testing decisions, and tiny working increments. Use when the user wants to plan a refactor, write a refactoring RFC, or turn a risky change into safe incremental work.

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

You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration paths for breaking changes.

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

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

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

Manages .NET release lifecycle. NBGV versioning, SemVer, changelogs, pre-release, branching.

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

Detects API surface changes in CI. PublicApiAnalyzers, Verify snapshots, ApiCompat gating.

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

Creates or updates the active planning artifact under planning/active/ for any change-bearing workstream. Consumes the active spec when one exists. Defines ordered tasks, target paths, commands, and checkpoints.

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

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

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

Produce and maintain repository documentation and release artifacts, including README files, PR descriptions, changelog entries, prompt templates, and instruction docs. Use when the user asks to create or update docs/process files under .github or project root.

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

Design, implement, and stabilize automated tests (unit, integration, E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.

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

Implement and refactor frontend features using Vue and Quasar with repository architecture, theming, UX, and performance standards. Use when tasks involve components, composables, Pinia, routing, i18n/UI behavior, responsive layouts, or frontend clean architecture changes.

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

Design, implement, and stabilize automated tests in this repository (unit, integration, and E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is reached.

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

Design and enforce privacy and data protection controls across application, API, and database layers. Use when tasks involve PII handling, retention/deletion policies, consent, data minimization, auditability, or compliance-oriented architecture changes.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

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