「commit」の検索結果

Run the read-only infra/lint PR reporter only when invoked by CI or explicitly requested; do not select it for the commit workflow's fix-and-respond review.

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

Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.

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

Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes). Use when packages/ or .changeset/ are modified, or when verifying PR changeset compliance and bump level.

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

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

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

Review a PipesHub pull request or diff for correctness, scalability, null safety, reuse, design and tests. Use when asked to review a PR, a branch, a commit or the current diff, and when CI runs the automated review.

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

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

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

Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready. Requires fresh verification output before success claims. Do not use for root-cause debugging, TDD implementation, test-report packaging, or review-feedback triage.

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

Socratic ideation and idea routing — think through ideas before committing to plans

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

Create a clean PR branch by filtering out .planning/ commits — ready for code review

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

Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.

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

Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit

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

Run CIAgent regression checks after changing an AI agent's code, prompts, or knowledge base in a repo that has agentci_spec.yaml, and interpret the results. Use after editing agent logic, before committing agent changes, or when the user asks whether the agent still works.

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

Commit the session to durable vault memory and prepare a clean resume point

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

Not for writing library code (name that library skill). Use this skill whenever another DOCA skill says "prefer the structured tool per doca-structured-tools-contract", or when the user wants a one-shot answer that consolidates info multiple manual commands would produce — DOCA env / version / devices / capabilities / validate / host vs DPU state. Trigger even when the user does not explicitly mention "structured tool" or "doca-env --json" — typical implicit phrasings include "is there one command that tells me everything about my DOCA install", "what version is X capability available since", "every PF/VF/SF visible on this BlueField with PCIe address", "will this pipe pass validate before commit", "diff host vs DPU state", or "why does the agent give a one-line answer on host A and five commands on host B". Refuse and route elsewhere for general DOCA orientation, specific library API how-to, or install-from-scratch guidance — those belong to the per-library skill, doca-public-knowledge-map, or doca-setup.

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

doca_telemetry_utils command line on a host with DOCA: discover the diagnostic-counter schema, translate counter names to binary Data IDs and back, and check per-device counter support before committing a DOCA Telemetry exporter config. Start here when telemetry counters vanish between the exporter and the collector: "my exporter ships but the collector sees nothing", "this metric silently drops downstream", "which counters does this BlueField expose", "translate this 0x... back to a counter name", "what do node / pcie_index / depth mean here", or "is this counter supported on this device", even without naming the tool. Writing exporter or collector code belongs to doca-telemetry-exporter / doca-telemetry; DTS deployment to doca-dts; DOCA install or repair to doca-setup.

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

Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what stays personal, and what the team-kit plugin adds. Use when someone asks how the team's Claude Code setup works or what they get by cloning the repository.

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

Review oh-my-hermes pull requests that have not been reviewed at their current head commit. Run manually to sweep the open backlog, or pass a number to review one PR. Applies the repository's REVIEW.md policy and posts findings as a GitHub review with inline comments.

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

[omh] Security event on the code already shipped -- a CVE in a dependency, a secret committed to the repo, a license question, an advisory: triage reachability and severity, contain in order, and never close a leaked secret before its rotation is observed. Use when the user says: security-event-response, security event response, cve, triage this cve, cve in our dependency, cve in a dependency, security advisory, dependabot alert.

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

[omh] Git branch in trouble -- a merge conflict, a commit that broke something, history to repair: plan the resolution, the bisect, or the rewrite, name what is already pushed first, and force-push only with `--force-with-lease`. Use when the user says: git-workflow, git workflow, merge conflict, merge conflicts, rebase conflict, resolve the conflict, resolve this conflict, conflict markers.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish

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

Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.

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

Research an app idea or resolve product and technical uncertainties before committing to a design.

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

Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.

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