「exe」の検索結果

APIや画面、データ処理などの特性に合わせて、必要なテストと優先順位を整理します。網羅性・実行速度・保守の負担を考慮し、具体例を含むテスト計画にまとめます。

• 新機能のテスト計画を作りたいとき
• 既存テストの不足を探したいとき
• APIや画面のテストを選びたいとき

FastGPTのワークフローノードを、既存フローの表示と実行を保ちながら非推奨にし、新規追加の一覧から外すための変更箇所と確認手順をまとめたスキル。

• FastGPTのノードを非推奨にしたいとき
• ノードの新規追加を止めたいとき
• 旧フローとの互換性を維持したいとき

FastGPTのPRを、変更目的と主要ロジックの確認から安全性・性能・テスト・互換性まで段階的に点検し、問題の重大度を整理した報告と行単位のコメントにまとめるスキル。

• マージ前のPRを点検したいとき
• 正常系・境界条件・異常系の検証
• APIやデータベースの互換性確認

FastGPTのコードに単体テストを追加し、基本動作から境界値・例外まで確認するスキル。テストの配置、外部依存の置き換え、型とカバレッジの検証を案内します。

• 関数に単体テストを追加したいとき
• 境界値や例外処理を確認したいとき
• API通信を含む関数のテスト

数学の概念や数式の導出、アルゴリズムの動きをアニメーションで説明する動画を制作します。構成づくりから描画、シーンの結合、仕上がりの確認まで扱います。

• 数学の概念を動画で説明したいとき
• 数式の導出を段階的に見せたいとき
• アルゴリズムの動きを可視化

会話で編集方針を決め、動画の文字起こし、カット、色調整、字幕やアニメーションの追加を進めます。プレビューの確認と修正を重ね、完成動画を書き出します。

• 説明動画の良いテイクを選びたいとき
• チュートリアルを短くして字幕を付けたいとき
• インタビューや旅行映像の編集

AIエージェントが業務ルールや権限を守るかを、試験シナリオで監査します。対象の設定整理から実行、選択したモデルによる採点と結果の説明まで案内します。

• 業務ルールへの対応を監査
• 権限の境界や危険なツールの扱いを検証
• HTTP経由でエージェントを試験

実モデルで起きるMastra Codeの不具合を再現し、通信から画面表示までの時刻付きログを比較して、応答順序や速度表示の異常が生じる箇所を調べるスキル。

• トークン速度表示の異常調査
• 実モデルで時々起きる不具合の再現
• 画面のちらつきや状態停止の調査

Authoring playbook for building agents that automate recurring internal tasks — running scheduled workflows, syncing data between systems, posting notifications, processing inbound events, or executing operational runbooks. Use this when the user wants an agent that runs on a schedule, reacts to events, automates a process, syncs between tools, or handles ops/internal infrastructure.

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

Produce a phased implementation plan for a Factory work item, then advance it to execute

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

Use early when debugging a medium or hard bug, especially when tests alone may not reveal the real runtime failure. Trigger this before extended TDD iteration when a bug involves runtime state, ordering, persistence, streaming, concurrency, UI/manual reproduction, external services, or when a red or newly passing test may not model the real issue. Skip only when the root cause is already directly proven by a stack trace or deterministic test that exercises the real runtime path.

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

Use when the user wants to add, write, debug, or configure a Crush hook — gating or blocking tool calls, approving or rewriting tool input before execution, injecting context into tool results, or troubleshooting hook behavior in crush.json.

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

Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use `/batch` followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait minutes to hours, you may suggest the user type `/batch-api` themselves for the half-price asynchronous Batch API — you cannot invoke it, and it is not suited to in-place edits or tasks needing tool feedback.

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

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

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

Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.

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

Pre-mortem plan analysis. Imagine the plan failed 12 months from now and work backwards to find the weaknesses. Surfaces assumptions, dependencies, and execution risks before committing resources. Use when before significant resource commitment, before presenting to a board or investors, when feedback has been one-sidedly positive, or when there is pressure to move fast and figure it out later.

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

ISO/IEC 42001:2023 AI Management System (AIMS) specialist for compliance teams running internal audits. Three decisions: (1) Where are the gaps against Clauses 4-10 and what do we close first? (2) What goes in the AI risk register and which Annex A controls treat each risk? (3) What's the 12-month internal audit plan that satisfies Clause 9.2? Use when preparing for certification, scoping internal audit cycles, or onboarding AI systems into an existing ISMS (27001) / QMS (13485) program. NOT an executive AI strategy skill (see chief-ai-officer-advisor). NOT EU AI Act compliance (see compliance-team-eu-ai-act).

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

Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2. Use when leading management reviews, setting quality policy and objectives, monitoring quality KPIs and cost of quality, or exercising QMR governance and regulatory oversight responsibilities.

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

Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017/745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.

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

Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it be done', 'run the delivery loop'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a full goal→plan→execute→verify→close delivery loop through the repo-wide agent-harness with Jira MCP data bridged into the domain's analytics tools. Distinct from product-team (what to build vs how to deliver it), business-operations (internal ops), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

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

Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.

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

Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.

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

Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

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

Full content production pipeline — takes a topic from blank page to published-ready piece. Use when you need to execute content: write a blog post, article, or guide end-to-end. Triggers: 'write a post about', 'draft an article', 'create content for', 'help me write', 'I need a blog post'. NOT for content strategy or calendar planning (use content-strategy). NOT for repurposing existing content (use content-repurposing). NOT for social captions only.

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