「merge」の検索結果

Post-review intake closing skill. After an intake is resolved (whether accepted via review/meta PR merge or rejected/deferred at triage/evidence review), run this skill to post standardized, personalized closing comments on the PR (if any) and each intake issue. Comments include: evidence pipeline findings with /trust-appraise TM output, per-row artifact scores, decisions rationale, path-to-promotion/acceptance guidance, and a mandatory badge status note including the universal Powered by Gaia badge. Use after curation completes, before or immediately after merge for accepted intakes, or immediately upon rejection.

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

Continuously monitor a GitHub PR for merge conflicts, CI failures, and CodeRabbit review comments, then automatically fix any issues found. Polls every 5 minutes and loops until every check is green. Use this skill whenever a PR has just been created or code has been pushed to a PR branch — it should be the default follow-up action after any PR creation or push. Also trigger on: "watch this PR", "guard this PR", "monitor CI", "keep fixing until green", "PRを監視して", "CIが通るまで 直して", /pr-guardian. When a PostToolUse hook reports that a push or PR creation just happened, proactively invoke this skill to start monitoring without waiting for the user to ask.

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.

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

Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.

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

Use when a task needs the judgment of an emergency medicine physician — risk-stratifying an undifferentiated chief complaint against a can't-miss diagnosis, deciding an ED disposition (discharge/observation/admit/transfer) under time and bed pressure, reasoning through EMTALA screening-and-stabilization obligations, or triaging a department under crowding/boarding load.

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

Use when a task needs the judgment of an Emergency Management Director — activating and staffing an EOC for a developing hazard, sequencing a disaster declaration and FEMA Public Assistance/Individual Assistance request, sizing shelter and resource needs against real population and capacity numbers, designing or critiquing a tabletop exercise, or writing an after-action report and improvement plan.

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

Reviews open Dependabot PRs, classifies by risk (patch/minor/major, security, lockfile-only), and merges safe ones or advises on what to do. Use when user mentions "dependabot", "dependabot PRs", "dependency updates", "merge dependabot", "review dependabot", "dependency PRs", "bump PRs", "update dependencies", or runs /dependabot-review command.

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

Use this whenever a downstream Vue project needs to absorb upstream Devkit Vue changes — triggers on "update stack", "sync with devkit", "merge upstream", "pull stack updates", "resolve stack conflicts". Two-phase: ISO merge (stack modules stay byte-identical to upstream) then project alignment (apply MIGRATIONS.md, diff project modules vs `tasks` reference, /verify). Stack-code failures get an issue on `pierreb-devkit/Vue`.

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

Audit an emergency resource management system for crisis readiness. Evaluates inventory tracking accuracy, deployment request-to-arrival pipeline, logistics and route optimization, supply chain resilience, inter-agency resource sharing (NIMS/EDXL), staging area management.

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

Use this skill to configure and manage NPSP Household Accounts: household naming rules, formal/informal greeting formats, primary contact designation, household merges, and household splits. Trigger keywords: NPSP household naming, household account not updating, merge duplicate households NPSP, household greeting customization, primary affiliation NPSP. NOT for FSC (Financial Services Cloud) households — use admin/household-model-configuration. NOT for bulk-loading constituents and households into NPSP — use data/constituent-data-migration.

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

Use when designing, reviewing, or troubleshooting Salesforce email templates, email alerts, and declarative notification design. Triggers: 'Lightning Email Template', 'email alert', 'merge field', 'org-wide email', 'too many emails', 'mass email limit'. NOT for migrating Classic templates to Lightning — use admin/classic-email-template-migration. NOT for sending email from Apex — use apex/apex-outbound-email-patterns.

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

Migrating Classic email templates (Text, HTML with Letterhead, Custom HTML, Visualforce email) to Lightning Email Templates (LET) and the Email Template Builder. Covers merge-field translation, Letterhead-to-Enhanced-Letterhead conversion, Visualforce email retention strategy, folder reorganization, sender-context (OrgWideEmailAddress) preservation, and downstream Email Alert / Process Builder / Flow rewiring. NOT for transactional Apex email sending (use apex/apex-outbound-email-patterns) or marketing email broadcasts (use Marketing Cloud / Account Engagement).

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

Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment. NOT for executing or troubleshooting the deployment itself - use admin/change-management-and-deployment. Also covers: the CAB charter (membership, quorum, decision rights), the CAB decision record artefact and its linter, the change classification matrix, the deployOptions a CAB decision pins (checkOnly, testLevel, rollbackOnError, ignoreWarnings, runTests), the 10-day quick-deploy validity window, the deploy-window vs freeze-register check, and the emergency (ECAB) path with its mandatory retrospective.

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

Find and flag duplicate or related [Gorgias](https://composio.dev/toolkits/gorgias) tickets that should be merged

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

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

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

Use when asked to babysit or watch a PR, when watching an open pull request, after opening or pushing to a PR, or when asked to monitor CI, review comments, merge conflicts, whether a PR is ready to merge, or to trigger a re-review.

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

serial-evidence-merge-target-parity

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

Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review this changeset", "is this ready to merge", "pre-merge review".

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

Coordinates release preparation for your monorepo — maintaining CHANGELOG and the release assessment document, resolving merge conflicts on release branches, and communicating status, risk, and asks to the broader team. Use when the user mentions release manager, release train, cut a release, release branch, CHANGELOG, release assessment, monorepo release, merge conflicts during release, versioning, or coordinating a version bump with engineering and stakeholders.

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

Prepare GEODE worktrees, Korean PRs, CI-gated merges, and guarded cleanup. Use for repository branch, commit, PR, merge, or release work; apply only the stages the user authorized.

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

git に関する全ての操作やこのプロジェクトのgitに関する情報が欲しい時に呼び出されるスキル（branch, commit, push, pull, merge ...）

Resolves an in-progress git merge/rebase conflict: reads conflict state, recovers each side's intent, resolves hunks, runs checks. NOT for the ship pipeline (mk:ship); NOT for bug debugging (mk:fix).

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

Decision-making patterns in incident command and emergency management leadership contexts

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

Handle mental health crisis situations in AI coaching safely. Use when implementing crisis detection, safety protocols, emergency escalation, or suicide prevention features. Activates for crisis keywords, safety planning, hotline integration, and risk assessment.

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