「ble」の検索結果

Scope, preregister, execute, audit, normalize, and publish GEODE evaluations with research-question, reproduction, attempt-lineage, trajectory, verifier-receipt, and immutable artifact contracts. Use for benchmark runs or comparisons, eval-artifact and cache-accounting audits, GPT or subscription result normalization, research question or hypothesis framing, retry diagnosis, trajectory publication, DPO or reward-data readiness reviews, and requests involving MCPMark, tau2, BFCL, Agent-World, HAL, Terminal-Bench, or Toolathlon.

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

Audit and improve Generative Engine Optimization as a measurable discovery-to-citation pipeline. Use for /geo, AI-search visibility, citation readiness, and GEO benchmark work.

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

Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".

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

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

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

Publish and verify a released GEODE version across GitHub Release and PyPI/uv. Use for uv/uvx distribution, stable promotions, release repair runs, and public installation-channel audits.

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

Reliable progress watching for long-running background commands (training runs, live audits, batch jobs, CI) without losing output to stdout buffering. Prefer post-completion cat-and-grep over tail -F.

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

Ground GEODE design and evaluation work in Stanford CS329A Parts 2 and 5. Use for test-time compute, planning, multi-step reasoning, deep research, LATS, independent subplans, best-of-N, repair depth, measurement replication, verifier authority, and GEODE/Eco²/SIL/Crucible comparisons.

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

Use an available Codex MCP integration as a read-only second-opinion verifier for GEODE code reviews, GAP audits, and contract checks. Use only when the user requests Codex cross-checking and the current tool inventory exposes the required MCP tools.

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

Reports how local Git branches are progressing toward canonical upstream inclusion as a compact terminal table plus a browser-rendered HTML report, with branch purpose, stack dependencies, Git Machete topology, ahead/behind counts, change-request status, and next action. Use when asked for upstreaming status, local branch submission progress, which branches have change requests, or what remains before they can land.

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

Use the Xero MCP server — troubleshoot its self-refreshing OAuth2 token file, maintain the local best-of-breed server build, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, before starting any Xero workflow, when adding or updating upstream xero-mcp-server PRs, or for general guidance on Xero MCP usage.

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

Turns an existing Product Requirements Prompt at .ai/[feature]/prp.md into a step-by-step task list of parent tasks and sub-tasks, saved to .ai/[feature]/tasks.md and committed. Use when a PRP is ready to be broken down into implementable work, or when planning how a feature will be built before any implementation starts. To write the PRP itself first, use prp- generation.

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

Prepare and publish upstream issues, feature requests, discussions, pull or merge requests, and patch submissions in the channel the canonical project expects. Use when reporting a problem upstream, requesting a feature, contributing a change, or asking to submit upstream.

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

Scan every open pull request in a GitHub repository, filter to the ones that are genuinely mergeable now, and report a compact verdict with a suggested merge order. Use when the user asks which PRs can be merged, wants an open-PR backlog triaged or reviewed in bulk, asks why a PR is blocked, or wants to clear a queue of stale or bot-reviewed PRs.

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

Capture durable project or workflow knowledge discovered during work. Use when a mistake, hidden constraint, repeated question, or changed behavior reveals a documentation gap. To root-cause one specific mistake the agent just made and let the user pick fixes, use `learn` (`/learn`) instead.

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

Corrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.

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

Plan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries. To triage an already-dirty working tree and propose commits for existing uncommitted changes, use `planning-commits` instead.

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

Generates a minimal .editorconfig with sensible defaults for a repository. Use when starting work in a new repository, when a project has no .editorconfig, or when the user asks to add or standardise editor and formatting settings.

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

Re-asks the most recent question through the agent's interactive questionnaire tool instead of plain text, and keeps using that tool for every later question with concrete options. Use when the user invokes `/qs` or `$qs`, or asks for a question to be re-posed as selectable choices.

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

Create and maintain agent skills with concise trigger metadata, judgement-aware guidance, progressive disclosure, and tested interfaces. Use when adding, refactoring, reviewing, or troubleshooting skills and their bundled scripts or references.

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

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

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

Gives a repository one idempotent, repo-local worktree setup script (local env files, dependency install, build steps) that worktrunk's `.config/wt.toml` pre-start hook and Orca's `orca.yaml` scripts.setup both call, so every new git worktree is usable at once. Use when adding or fixing worktree setup hooks, writing `wt.toml` or `orca.yaml` setup, when new worktrees lack dependencies or `.env` files, or when asked to make worktrees "just work" in a repo. For creating a worktree in a repo that already has setup, use `git-branch-management` instead.

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

Decompose an approved implementation plan into self-contained beads issues with zero guesswork. Use when breaking down a plan file into actionable beads tasks.

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

Decompose an approved implementation plan into self-contained Linear issues with zero guesswork. Use when breaking down a plan into actionable Linear tasks via the MCP server.

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

Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.

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