「merge」の検索結果

Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit approval. Use on "QA scope for PROJ-123", "what should QA test", "write test scenarios for QA", "hand this ticket to QA", "prep the QA handoff", "gherkin scenarios for this ticket", or when a branch is ready for manual testing — even when the user only names the ticket or says "this branch".

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

Audit and maintain the learnings in `docs/solutions/` against the current codebase — fix drifted paths and links, merge overlapping docs, replace guidance the code no longer supports, delete obsolete docs, reconcile the `CONCEPTS.md` glossary, then report and commit. Also bootstraps `CONCEPTS.md` on request and, when asked, culls docs whose reasoning the code already explains. Use for "refresh the learnings", "audit docs/solutions", "are our solution docs still accurate", "clean up / prune the learnings", "create a CONCEPTS.md", or after a refactor, rename, migration, or dependency upgrade that likely invalidated documented solutions. Not for capturing a new learning — use `learn-with-docs`.

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

Review a dygo Business App for framework conventions, model quality, access control, SDK boundaries, observability, and safe lifecycle behavior. Use for App audits and pre-merge reviews, not ordinary implementation.

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

Complete shadcn/ui component management for adding, searching, fixing, styling, and composing UI in any React project. Use this skill whenever the user mentions shadcn, shadcn/ui, adding UI components, building forms or dashboards with Radix, working with component registries (@shadcn, @magicui, @tailark), or any task involving npx shadcn CLI commands. Also trigger when the user asks to fix styling issues, build a settings page, dashboard, or modal flow in a project that uses shadcn/ui — even if they don't say "shadcn" explicitly. This skill manages the full component lifecycle: search, add, view, diff, smart-merge upstream updates, and enforce critical rules for forms, composition, styling, and icons.

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

Cycle horaire du coordinateur adjoint myia-po-2025:CoursIA-2. Réduit la file, répond aux ASK CoursIA-2, publie des preflights COMMENTED et dispatche les lanes CoursIA-2, sans merge ni arbitrage réservé à ai-01.

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

Cycle de coordination ai-01 (coordinateur UNIQUEMENT — jamais sur un worker). Lit memoire + dashboards + inbox + GitHub, merge les PRs pretes, tranche les design-gates, dispatche des grains par lane, reporte. Arguments: [--dispatch] [--focus <topic>]

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

Review and merge student exercise PRs during TP sessions. Arguments: <repo-url> [--class <class-id>] [--timeslot <HH:MM-HH:MM>] [--dry-run]

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

Persistent vector memory for Claude Code via LanceDB. Use when: remembering across sessions, storing lessons, recalling past decisions, maintaining context continuity. Tools: memory_store, memory_recall, memory_update, memory_forget, memory_merge.

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

Delegate implementation work to a dedicated implementer subagent, then review its diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants a separate model to write code, mentions handing off / delegating implementation, asks to work through a plan or spec unit-by-unit with a subagent doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer self-reports success, must not run the full test suite by default, must not touch git, and its report is a claim rather than evidence. Cursor port of implementation-loop. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the cursor-engineering-mode skill (it ships in this same plugin).

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

Delegate implementation to Codex, grok, or cursor-agent, then review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex, the grok 后端, or cursor-agent to write code, mentions handing off / delegating implementation to one of those backends, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.

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

Diagnose and repair a failed GEODE smoke workflow within the requested acceptance criteria. Preserve failed evidence, verify the shared root cause, and apply merge, rebuild, or live rerun stages only when authorized.

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

GEODE evidence-first development workflow. Use for feature work, provider/model changes, GUI/computer-use work, PDF/document ingestion, observability/schema/event/state changes, verification planning, GitFlow merge prep, and requests to "follow the workflow" or "scaffold the process".

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

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.

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

Checks the canonical upstream issue tracker, discussion forums, and open pull requests, merge requests, or equivalent change queues for existing reports, discussion, or work on a problem just discussed. Use before diagnosing, fixing, or reporting an apparent open-source problem to avoid duplicate effort and missed context.

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

Rebases every local branch of a fork onto a moved upstream, flags the ones upstream has superseded, and rebuilds the mixdown branch that combines them. Use after fetching a fork's upstream and finding it has advanced far, been force-pushed, or rewritten its history; when several stacked or sibling branches all need bringing forward at once; when a branch was cut from a mixdown and now carries merge commits it should not have; or when asked to rebase all branches, re-mix, or bring a whole worktree set up to date.

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

Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.

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

GitLab workflow automation with the glab CLI — merge requests, issues, CI, releases, and safe message escaping. Auth via GITLAB_TOKEN (set in global settings, attached to the sandbox env).

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

Configura el repositorio de GitHub de punta a punta con gh — descripción, topics, labels, rama develop, protección de ramas, merge settings y metadatos — a partir de la definición del producto. Úsalo al crear el repo de un proyecto nuevo o cuando haya que poner en orden uno existente (p. ej. "configura el repo", "prepara el repositorio en GitHub", "pon los labels y la protección de ramas").

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

Redacta un pull request para la rama actual rellenando la plantilla de PR del repositorio en función de los cambios de la rama. Úsalo cuando la persona pida abrir/crear un PR, preparar un pull request o escribir la descripción de un PR (p. ej. "abre un PR", "redacta el pull request de esta rama"). No hace merge.

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

Drafts a Chapter 11 Plan of Reorganization under 11 U.S.C. §§ 1121–1129 with claim classification, treatment provisions, distribution mechanics, executory contract determinations, and confirmation compliance. Use when preparing reorganization plans, restructuring debts, classifying claims, drafting Chapter 11 plans, or helping debtors emerge from bankruptcy. Trigger keywords: reorganization plan, Chapter 11, plan of reorganization, debt restructuring, cramdown, claim classification, confirmation order.

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

Produces a plain-language comparison of advance directives and POLST/MOLST forms, covering legal status, clinician signatures, emergency precedence, clinical appropriateness, and document coordination. Use when the user asks about advance directive vs. POLST, living will vs. DNR, which document EMS follows, POLST vs. MOLST vs. POST, whether a healthy person needs a POLST, or document coordination in elder law, estate planning, or serious illness contexts.

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

Manages git worktrees for parallel agent isolation: creates parallel/{name}-{timestamp} branches, merges with conflict detection. NOT for user feature branches (use git worktree directly).

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

GitHub project management via gh CLI: issues, Projects v2 boards, labels, milestones, handoff summaries. NOT for code review (mk:review-pr), PR creation, or git ops (mk:resolving-merge-conflicts).

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

Ship workflow with explicit scopes: prepare stages and commits locally; release pushes and creates a PR; publish manages issues and versioning. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying. Supports official (→ main) and beta (→ dev/develop) ship modes with auto-detection.

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