「merge」の検索結果

Independent re-derivation gate for proposed changes during autonomous execution. Evaluates a change (code diff, config edit, engine evolution, schema change) against the work's authority matrix and a 4-check protocol: invariant compliance, scope authorization, detection narrowness, and regression risk. Returns structured JSON with pass/fail per check, an overall verdict (APPROVE / REQUEST_CHANGES / REJECT), and blockers. Profile-driven thresholds (strict for unattended runs, lenient for desk supervision). Use when an autonomous agent proposes an engine change, when reviewing a Claude Code-authored modification before merge, or when an unattended profile requires independent re-derivation. Trigger on: "review/approve this proposed change," "critic-gate this," "is this change safe," "is this safe to merge," "should I let this land," "run the critic." Do NOT use for handoff-readiness checks (use rootnode-handoff-trigger-check), general code review, or design-time correctness. Authority matrix required.

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

Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.

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

Create, merge, and deduplicate BibTeX bibliography files using R packages (RefManageR, bibtex). Parse .bib files into structured R objects, merge multiple bibliographies with deduplication by DOI or title similarity, generate entries from DOI/ISBN/arXiv ID, and export clean sorted .bib files. Use when creating a new .bib file for an R Markdown or Quarto project, merging bibliographies from multiple collaborators, deduplicating a .bib that has grown through copy-paste accumulation, or generating BibTeX entries programmatically from DOIs or other identifiers.

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

Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval and retrospective documentation.

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

Form a coherent gestalt — the whole that is more than the sum of its parts — from the panoramic perception produced by expand-awareness. Maps tensions and resonances between domains, identifies the emergent figure from the ground of multiple perspectives, tests the candidate whole for premature closure, and articulates the insight in a single sentence no single domain could have produced. Use after expand-awareness has surfaced raw multi-domain perception and before express-insight communicates the result.

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

AI unconstrained creative exploration — deliberately dropping structure to let associations form freely. The one skill that inverts the standard procedure format: instead of inputs, steps, and validation, dream opens space for emergence without evaluation. Use before design work, before naming things, before choosing between approaches, or anywhere that premature structure kills the best option.

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

Creation and genesis — generative ideation from void, structured emergence from ambiguity, and the discipline of bringing new patterns into existence. Maps Brahma's creative power to AI reasoning: transforming cleared space into coherent new structures, seeding possibilities, and nurturing nascent ideas through their fragile early stages. Use after shiva-bhaga dissolution has cleared stale patterns, when facing a genuinely novel problem with no obvious template, or when incremental modification has reached its limits and a fresh design is needed.

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

Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.

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

Use when a human explicitly invokes a watcher cycle for an open pull request that must be watched until mergeable or blocked. Not for merge, force-push, or work outside the invoked cycle.

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

Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts. Not for people-mediation conflicts: use culture-conflict-mediation.

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

Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.

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

Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.

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

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push".

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

Software Factory 2026秋の開発フローをこのsessionに適用する。 着手前に不明点をユーザーに質問、変更が一段落したらcodexでbug確認、draft PR作成、対話コンテキストexport、インラインレビューコメントの草稿、ユーザーの指示でsanity-review、ready for review後のsquash and mergeのcommit message草稿の提示、という進め方を定める。 開発の開始時にユーザーが手動で起動する。

Use when you need to resolve an in-progress git merge/rebase conflict.

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

Pull the latest remote base branch into the current local branch and resolve merge conflicts (aka update-branch). Use when the agent needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.

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

Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.

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

Reviews pull requests for overall quality before merging. Combines code quality and security checks at PR level. Use when performing pre-merge review in Operations Phase.

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

Use when you need to resolve an in-progress git merge/rebase conflict.

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

Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.

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

"Apply Complex Adaptive Systems theory to analyze phenomena exhibiting emergence, self-organization, co-evolution, and edge-of-chaos dynamics. Use this skill when the user needs to understand why a system behaves unpredictably despite known components, model agent-based interactions that produce emergent outcomes, analyze fitness landscapes, or when they ask 'why does this system behave in ways no one designed', 'how do local interactions create global patterns', or 'why do small changes sometimes cause massive system shifts'.".

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

Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".

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

Run post-merge release build steps for this repository, including Android tag-driven releases and sequential iOS IPA generation with archival for Transporter upload and Crashlytics deobfuscation. Use after the release PR has been merged.

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

Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent / diamond-convergence conflicts, and configure environment refs for CI. Use for "what migrations are going to run", "what runs on deploy", merge conflict, diamond convergence, concurrent migrations, migration status, ref management, staging, production, MIGRATION.DIVERGED, MIGRATION.NO_MARKER, MIGRATION.MARKER_NOT_IN_HISTORY, prisma migrate status, prisma migrate diff, prisma migrate resolve.

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