warpdotdev/resolve-merge-conflicts

Résoudre les conflits de fusion Git en extrayant uniquement les chemins non résolus, les blocs de conflit et les diffs compacts, sans charger les fichiers entiers dans le contexte. Utilisez-le lorsqu'une fusion, un rebasage, un cherry-pick ou un stash pop s'arrête sur des conflits, lorsque `git status` affiche des chemins non fusionnés, ou lorsque les fichiers contiennent des marqueurs de conflit.

Qu'est-ce que resolve-merge-conflicts ?

Cette compétence pour agents IA (telle que Claude Code, Cursor, Codex) permet de résoudre efficacement les conflits de fusion Git. Au lieu de charger l'intégralité des fichiers dans le contexte, elle extrait uniquement les chemins non résolus, les blocs de conflit (hunks) et les diffs compacts. Cela réduit considérablement la consommation de tokens et permet à l'agent de se concentrer sur les parties conflictuelles. La compétence est utile lors d'une fusion, d'un rebasage, d'un cherry-pick ou d'un stash pop qui s'arrête en raison de conflits, ou lorsque `git status` montre des chemins non fusionnés ou que des marqueurs de conflit sont présents dans les fichiers. Elle fonctionne sur les plateformes supportant les agents IA comme Claude Code, Cursor et Codex.

Compatible avec~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/resolve-merge-conflicts

Installed? Explore more Développement et programmation skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Que fait resolve-merge-conflicts ?

Résolvez les conflits de fusion Git en extrayant uniquement les chemins non résolus, les blocs de conflit et les diffs compacts, au lieu de charger les fichiers entiers dans le contexte. Utilisez-le lorsqu'une fusion, un rebasage, un cherry-pick ou un stash pop s'arrête sur des conflits, lorsque git status affiche des chemins non fusionnés, ou lorsque les fichiers contiennent des marqueurs de conflit.

Individual skills in this repo

This repo contains 16 individual skills — each has its own dedicated page.

warpdotdev/brandalf

Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.

warpdotdev/check-impl-against-spec

Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.

warpdotdev/council

Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.

warpdotdev/create-pr

Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

warpdotdev/diagnose-ci-failures

Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

warpdotdev/fix-errors

Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.

warpdotdev/implement-specs

Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.

warpdotdev/pr-walkthrough

Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.

warpdotdev/reproduce-bug-report

Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.

warpdotdev/respond-to-pr-comments-in-blocklist

Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.

warpdotdev/review-pr

Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.

warpdotdev/spec-driven-implementation

Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.

warpdotdev/update-skill

Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.

warpdotdev/validate-changes-match-specs

Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.

warpdotdev/write-product-spec

Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

warpdotdev/write-tech-spec

Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.

Skills associés