「ker」の検索結果

Use when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done", "finish while I am away", "do not ask questions unless truly blocked", or similar. Convert ordinary ambiguity into stated assumptions, proceed through implementation and validation, stop only for true blockers, and end with a clear recap of decisions, changes, verification, and residual risk.

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

Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory

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

Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.

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

Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage

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

Launch a new bb worker thread with the right project, model, worktree, and task brief. Use for nagent, launching a bb session, or a standalone bb agent. Covers thread creation; use bb-cli for managing existing threads.

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

Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. panel-mode (full | lean | delta) selects a surface-gated roster plus a CEO synthesizer; omitted or unknown mode is lean. Do not spawn inactive stubs. The orchestrator is the sole writer to the PR: ONE recommendation comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes follow-ups, and renders a ship-recommendation that the maintainer and author weigh.

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

Use this skill to queue maintainer-accepted microsoft/apm issues (`status/accepted`) and fan them out through an isolated pool (default 2) of autopilot-issue-delivery-worker sessions. Any accepted type is eligible. Advisory `triage/recommended` is not authorization. Does not triage. Does not review PRs. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.

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

Use this skill to triage ONE microsoft/apm issue already selected by autopilot-issue-triage-scheduler. Return one advisory recommendation and a proposed scope brief, never human approval. Do not implement the issue, manage the backlog, or list the queue.

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

Use this skill to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler. Queue signal is `status/accepted` or a named bounded accept; that is not permission. Requires fresh human-scope evidence from scripts/governance before any mutate. May reproduce a bug, implement the accepted change, and open a fix PR. Not a queue manager and not a triage scheduler. Works in the scheduler's session, a child session, Cloud Agent, Remote Agent, or Agentic Workflow.

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

Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-writer + python-architect + editorial-owner + growth-hacker loop to produce a patch-ready advisory. Does NOT review code quality, security, or test coverage. Does NOT auto-merge or auto-push doc edits.

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

Queue open microsoft/apm issues and fan them out through an isolated pool (default 2) of autopilot-issue-triage-worker sessions. Advisory only. Never implements, never assigns, never requests reviewers. Activate on a mixed issue list or queue-all when the job is triage. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.

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

Deploy a significant code change (backend, kernel, optimizer, data path) to the live hero run: relaunch it under a new run id from a permanent checkpoint, compare against the old run over a trial window, and roll back if the gate fails; use only when the user asks to deploy a change to the hero.

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

Query Finelog logs and telemetry for Iris tasks, workers, profiles, training, vLLM, and cross-cluster forwarding. Use for schema discovery, SQL, memory or CPU summaries, hub-versus-regional comparisons, counter semantics, and query-performance diagnosis.

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

XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs that shouldn't be in a sitemap, plus indexable pages that are missing from it. Reviews lastmod accuracy, sitemap-index organization, and robots.txt reference. Use this skill whenever the user asks about sitemaps, sitemap errors in Search Console, "sitemap couldn't fetch / has errors", crawl budget, pages not getting indexed, or whether their sitemap is clean. Trigger on: "sitemap", "sitemap.xml", "XML sitemap", "sitemap errors", "sitemap audit", "couldn't fetch sitemap", "crawl budget", "pages not indexed sitemap", "sitemap index", "lastmod", "robots.txt sitemap", or any sitemap/crawl-coverage question. For a full-site SEO audit use /seo-analysis; for broken links use /broken-link-checker.

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

Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".

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

Check if specific lines were executed using gcov data

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

Open or file a GitHub issue, bug report, feature request, docs issue, or chore. Add evidence to an existing issue. Run gh issue create or gh issue comment.

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

Invoke this skill when the user says "use btca"

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

Verify PR #N, does this PR fix #M, check the fix in #N, or test the candidate PR.

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

Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push

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

Triage backlog, scan open issues, rank what to tackle first, or which PRs are production-ready.

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

Reproduce #N, investigate #N, try #N locally, or verify the bug in #N.

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

Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server. Use only for an explicit LinkedIn request.

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

社媒数据记录与趋势分析。三种模式：(A) 记录快照 — 记录当日粉丝数、互动量等指标快照； (B) 增长趋势 — 分析粉丝增长率、增速变化、里程碑预测；(C) 内容生命周期 — 追踪单条内容 从发布到衰减的数据变化，判断速爆型/稳增型/长尾型。当用户说"记录数据"、"今天粉丝数"、 "增长趋势"、"粉丝增长"、"内容生命周期"、"这条笔记数据变化"、"数据快照"时触发。

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