[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQWJ97TMM1D04FKAFAXSMT":3,"skill-same:01M7CQWJ97TMM1D04FKAFAXSMT":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7CQWJ97TMM1D04FKAFAXSMT","agent-merge-conflict-arbiter",null,"Neutral arbiter for merge conflicts between two agents.","thalhath2234\u002Ftimely-app","thalhath2234","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69391707?v=4","01M7CQNWTHSAP0D50RQY6W9YZQ","Thalhath","01M7CQNWVQN600VKQXRGTWCDPH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Fhermes\u002Foptional-skills\u002Fautonomous-ai-agents\u002Fagent-merge-conflict-arbiter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-merge-conflict-arbiter\ndescription: \"Neutral arbiter for merge conflicts between two agents.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Multi-Agent, Git, Merge-Conflict, Kanban, Arbitration]\n    related_skills: [hermes-agent]\n---\n\n# Agent Merge-Conflict Arbiter\n\nResolve a git merge conflict between two AGENTS' branches as an impartial third\nparty. Agents resolving conflicts against a peer's work reliably either\noverwrite the peer or abandon their own change — they lack the peer's context\nand are biased toward their own side. This skill is the fix: a neutral\nreconciler that receives both diffs plus both sides' stated intents and\nproduces a merged result, like a merge-queue arbiter.\n\n## When to Use\n\n- Two agent branches\u002Fworktrees collide during a parallel campaign (kanban\n  engineering pipeline, parallel-PR wave, multi-worktree refactor).\n- `git merge` or `git rebase` halts on conflicts between two agents' work and\n  neither original agent should self-adjudicate.\n- Do NOT use for conflicts within a single agent's own work, or for trivial\n  lockfile\u002Fgenerated-file conflicts (regenerate those instead).\n\n## Prerequisites\n\n- A repo checkout containing the halted merge, or the two branch names plus\n  permission to run the merge yourself.\n- Both sides' intent sources: kanban completion summaries (`terminal` running\n  `hermes kanban show \u003Ctask-id>`), PR bodies, or at minimum each branch's\n  commit messages.\n- The project's build\u002Ftest command, if one exists.\n\n## How to Run\n\n**Standalone** — a human (or agent) invokes this skill inside the conflicted\nrepo: load the skill, then follow the Procedure top to bottom.\n\n**Spawned neutral agent** — the preferred shape in multi-agent campaigns:\n\n- `delegate_task`: spawn a subagent whose task message contains the repo path,\n  both branch names, and both sides' intent summaries verbatim, plus an\n  instruction to follow this skill.\n- Kanban-native: create a reconciliation card assigned to a **third profile**\n  (not either worker's profile) with BOTH conflicted cards linked as parents —\n  `kanban_create(title=\"reconcile branch-a x branch-b\", assignee=\"reconciler\",\n  parents=[\"t_a\", \"t_b\"])`. The parent links carry both sides' completion\n  summaries into the reconciler's context automatically; the card body should\n  name the repo path and the two branches.\n\n## Quick Reference\n\n| Hunk class | Definition | Resolution |\n|---|---|---|\n| disjoint-intent | The two changes serve different goals and can coexist | Combine both |\n| same-question-different-answer | Both sides answered one design question differently | Pick ONE per stated intents; surface the decision |\n| superseded | One side's premise no longer holds after the other's change | Keep the surviving side; note why |\n\nImpartiality contract: never favor the side that spawned you; touch ONLY\nconflicted regions (no drive-by edits); every design-question pick must appear\nexplicitly in the hand-back summary.\n\n## Procedure\n\n### 1. Gather both sides\n\n- Run via `terminal`: `git status` (confirm the conflicted state and list\n  conflicted files), `git merge-base \u003CA> \u003CB>`, then for each side\n  `git log --oneline \u003Cbase>..\u003Cside>` and `git diff \u003Cbase>..\u003Cside> -- \u003Cfile>`\n  for every conflicted file. In a halted merge, `HEAD` is one side and\n  `MERGE_HEAD` is the other.\n- Collect each side's intent: `hermes kanban show \u003Ctask-id>` for completion\n  summaries\u002Fmetadata, or the PR body, or the commit messages from the log\n  above. Write down one sentence of intent per side before touching any file.\n- Done when: you can state both intents in your own words and have both diffs\n  for every conflicted file.\n\n### 2. Classify every conflicted hunk\n\n- Open each conflicted file with `read_file` and locate each\n  `\u003C\u003C\u003C\u003C\u003C\u003C\u003C`\u002F`=======`\u002F`>>>>>>>` block.\n- Assign each hunk exactly one class from the Quick Reference table, judging\n  by the stated intents — not by which change looks nicer.\n- If a single hunk contains multiple independent decisions (e.g., new logic\n  that combines cleanly PLUS a styling\u002Frounding choice both sides answered\n  differently), decompose it into sub-decisions and classify each one.\n- A single file often mixes classes: one hunk may be a design collision while\n  a neighboring hunk is disjoint. Classify per hunk, not per file.\n- Done when: every hunk has a written class and a one-line rationale.\n\n### 3. Resolve under the impartiality contract\n\n- Edit each hunk with `patch` (or `write_file` for whole-file rewrites):\n  - disjoint-intent → merge both changes so each intent is fully served.\n  - same-question-different-answer → pick the answer that best serves the\n    STATED intents (e.g., an intent of \"strict validation\" beats \"quick\n    default\" if the task required correctness). Never split the difference\n    into a hybrid neither side asked for.\n  - superseded → keep the surviving side; delete the dead premise.\n- Never favor the side that spawned you. If intents genuinely tie, escalate\n  (block the kanban card \u002F report back) rather than guess.\n- Change nothing outside conflict markers — no formatting, renames, or\n  opportunistic fixes.\n- `git add` each resolved file via `terminal`.\n- Done when: `search_files` finds no `\u003C\u003C\u003C\u003C\u003C\u003C\u003C` markers in the repo and every\n  resolved file is staged.\n\n### 4. Verify\n\n- Run the project's build\u002Ftests via `terminal`; at minimum import\u002Fexecute the\n  touched modules. Both intents must be observable in the merged behavior\n  (e.g., side A's new semantics AND side B's disjoint addition both present).\n- Complete the merge: `git commit` (the default merge message plus a body\n  listing hunk decisions is fine).\n- Done when: verification passes and the merge commit exists.\n\n### 5. Hand back\n\n- Produce a completion summary naming EVERY hunk decision:\n  `file:lines — class — which side(s) kept — rationale`. For every\n  same-question-different-answer hunk, state the design question and the\n  answer you picked so a human can veto it — never bury a design call.\n- Kanban: `kanban_complete(summary=...)`. Standalone: print the summary.\n- Done when: the summary is delivered and lists all hunks.\n\n## Pitfalls\n\n- **Self-favoring**: if you were spawned by one of the conflicting agents,\n  you are structurally biased — state this and weigh the other side's intent\n  deliberately. Prefer the third-profile shape so this never arises.\n- **Splitting the difference** on a design collision produces a hybrid nobody\n  designed; pick one answer and surface it.\n- **Per-file classification**: files usually mix hunk classes; classifying a\n  whole file as one class silently drops a disjoint change.\n- **Drive-by edits** make the merge unreviewable and steal decisions from the\n  original agents.\n- **Missing intents**: commit messages alone can be thin; prefer kanban\n  completion summaries or PR bodies. If neither side's intent is recoverable,\n  escalate instead of guessing.\n- **Repeat offenders**: repeated conflicts on the SAME file across rounds are\n  a hotspot signal, not routine reconciliation work — flag it (e.g. a\n  `hotspot: \u003Cpath> — \u003Creason>` kanban comment) so the orchestrator decomposes\n  that file, rather than serially reconciling every new collision on it.\n\n## Verification\n\n- `git status` shows a clean tree on the target branch with a merge commit.\n- No conflict markers remain (`search_files` pattern `\u003C\u003C\u003C\u003C\u003C\u003C\u003C`).\n- Build\u002Ftests pass; both sides' intents are demonstrably present or the\n  dropped one is explicitly named in the summary.\n- The hand-back summary enumerates every hunk with class and rationale.\n","# Agent Merge-Conflict Arbiter\n\nResolve a git merge conflict between two AGENTS' branches as an impartial third\nparty. Agents resolving conflicts against a peer's work reliably either\noverwrite the peer or abandon their own change — they lack the peer's context\nand are biased toward their own side. This skill is the fix: a neutral\nreconciler that receives both diffs plus both sides' stated intents and\nproduces a merged result, like a merge-queue arbiter.\n\n## When to Use\n\n- Two agent branches\u002Fworktrees collide during a parallel campaign (kanban\n  engineering pipeline, parallel-PR wave, multi-worktree refactor).\n- `git merge` or `git rebase` halts on conflicts between two agents' work and\n  neither original agent should self-adjudicate.\n- Do NOT use for conflicts within a single agent's own work, or for trivial\n  lockfile\u002Fgenerated-file conflicts (regenerate those instead).\n\n## Prerequisites\n\n- A repo checkout containing the halted merge, or the two branch names plus\n  permission to run the merge yourself.\n- Both sides' intent sources: kanban completion summaries (`terminal` running\n  `hermes kanban show \u003Ctask-id>`), PR bodies, or at minimum each branch's\n  commit messages.\n- The project's build\u002Ftest command, if one exists.\n\n## How to Run\n\n**Standalone** — a human (or agent) invokes this skill inside the conflicted\nrepo: load the skill, then follow the Procedure top to bottom.\n\n**Spawned neutral agent** — the preferred shape in multi-agent campaigns:\n\n- `delegate_task`: spawn a subagent whose task message contains the repo path,\n  both branch names, and both sides' intent summaries verbatim, plus an\n  instruction to follow this skill.\n- Kanban-native: create a reconciliation card assigned to a **third profile**\n  (not either worker's profile) with BOTH conflicted cards linked as parents —\n  `kanban_create(title=\"reconcile branch-a x branch-b\", assignee=\"reconciler\",\n  parents=[\"t_a\", \"t_b\"])`. The parent links carry both sides' completion\n  summaries into the reconciler's context automatically; the card body should\n  name the repo path and the two branches.\n\n## Quick Reference\n\n| Hunk class | Definition | Resolution |\n|---|---|---|\n| disjoint-intent | The two changes serve different goals and can coexist | Combine both |\n| same-question-different-answer | Both sides answered one design question differently | Pick ONE per stated intents; surface the decision |\n| superseded | One side's premise no longer holds after the other's change | Keep the surviving side; note why |\n\nImpartiality contract: never favor the side that spawned you; touch ONLY\nconflicted regions (no drive-by edits); every design-question pick must appear\nexplicitly in the hand-back summary.\n\n## Procedure\n\n### 1. Gather both sides\n\n- Run via `terminal`: `git status` (confirm the conflicted state and list\n  conflicted files), `git merge-base \u003CA> \u003CB>`, then for each side\n  `git log --oneline \u003Cbase>..\u003Cside>` and `git diff \u003Cbase>..\u003Cside> -- \u003Cfile>`\n  for every conflicted file. In a halted merge, `HEAD` is one side and\n  `MERGE_HEAD` is the other.\n- Collect each side's intent: `hermes kanban show \u003Ctask-id>` for completion\n  summaries\u002Fmetadata, or the PR body, or the commit messages from the log\n  above. Write down one sentence of intent per side before touching any file.\n- Done when: you can state both intents in your own words and have both diffs\n  for every conflicted file.\n\n### 2. Classify every conflicted hunk\n\n- Open each conflicted file with `read_file` and locate each\n  `\u003C\u003C\u003C\u003C\u003C\u003C\u003C`\u002F`=======`\u002F`>>>>>>>` block.\n- Assign each hunk exactly one class from the Quick Reference table, judging\n  by the stated intents — not by which change looks nicer.\n- If a single hunk contains multiple independent decisions (e.g., new logic\n  that combines cleanly PLUS a styling\u002Frounding choice both sides answered\n  differently), decompose it into sub-decisions and classify each one.\n- A single file often mixes classes: one hunk may be a design collision while\n  a neighboring hunk is disjoint. Classify per hunk, not per file.\n- Done when: every hunk has a written class and a one-line rationale.\n\n### 3. Resolve under the impartiality contract\n\n- Edit each hunk with `patch` (or `write_file` for whole-file rewrites):\n  - disjoint-intent → merge both changes so each intent is fully served.\n  - same-question-different-answer → pick the answer that best serves the\n    STATED intents (e.g., an intent of \"strict validation\" beats \"quick\n    default\" if the task required correctness). Never split the difference\n    into a hybrid neither side asked for.\n  - superseded → keep the surviving side; delete the dead premise.\n- Never favor the side that spawned you. If intents genuinely tie, escalate\n  (block the kanban card \u002F report back) rather than guess.\n- Change nothing outside conflict markers — no formatting, renames, or\n  opportunistic fixes.\n- `git add` each resolved file via `terminal`.\n- Done when: `search_files` finds no `\u003C\u003C\u003C\u003C\u003C\u003C\u003C` markers in the repo and every\n  resolved file is staged.\n\n### 4. Verify\n\n- Run the project's build\u002Ftests via `terminal`; at minimum import\u002Fexecute the\n  touched modules. Both intents must be observable in the merged behavior\n  (e.g., side A's new semantics AND side B's disjoint addition both present).\n- Complete the merge: `git commit` (the default merge message plus a body\n  listing hunk decisions is fine).\n- Done when: verification passes and the merge commit exists.\n\n### 5. Hand back\n\n- Produce a completion summary naming EVERY hunk decision:\n  `file:lines — class — which side(s) kept — rationale`. For every\n  same-question-different-answer hunk, state the design question and the\n  answer you picked so a human can veto it — never bury a design call.\n- Kanban: `kanban_complete(summary=...)`. Standalone: print the summary.\n- Done when: the summary is delivered and lists all hunks.\n\n## Pitfalls\n\n- **Self-favoring**: if you were spawned by one of the conflicting agents,\n  you are structurally biased — state this and weigh the other side's intent\n  deliberately. Prefer the third-profile shape so this never arises.\n- **Splitting the difference** on a design collision produces a hybrid nobody\n  designed; pick one answer and surface it.\n- **Per-file classification**: files usually mix hunk classes; classifying a\n  whole file as one class silently drops a disjoint change.\n- **Drive-by edits** make the merge unreviewable and steal decisions from the\n  original agents.\n- **Missing intents**: commit messages alone can be thin; prefer kanban\n  completion summaries or PR bodies. If neither side's intent is recoverable,\n  escalate instead of guessing.\n- **Repeat offenders**: repeated conflicts on the SAME file across rounds are\n  a hotspot signal, not routine reconciliation work — flag it (e.g. a\n  `hotspot: \u003Cpath> — \u003Creason>` kanban comment) so the orchestrator decomposes\n  that file, rather than serially reconciling every new collision on it.\n\n## Verification\n\n- `git status` shows a clean tree on the target branch with a merge commit.\n- No conflict markers remain (`search_files` pattern `\u003C\u003C\u003C\u003C\u003C\u003C\u003C`).\n- Build\u002Ftests pass; both sides' intents are demonstrably present or the\n  dropped one is explicitly named in the summary.\n- The hand-back summary enumerates every hunk with class and rationale.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":36,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"Multi-Agent","Git","Merge-Conflict","Kanban","Arbitration",[35],"hermes-agent",[37,38,39],"linux","macos","windows","dev","4d9b346961dd1d220a07fe4e6ed44b52daa57e0b","apps\u002Fagent\u002Fhermes\u002Foptional-skills\u002Fautonomous-ai-agents\u002Fagent-merge-conflict-arbiter","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app","https:\u002F\u002Fgithub.com\u002Fthalhath2234","2026-11-14 05:26:10",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add thalhath2234\u002Ftimely-app --skill agent-merge-conflict-arbiter",{"tool":52,"command":53},"bunx","bunx skills add thalhath2234\u002Ftimely-app --skill agent-merge-conflict-arbiter",{"tool":55,"command":56},"pnpm","pnpm dlx skills add thalhath2234\u002Ftimely-app --skill agent-merge-conflict-arbiter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Fhermes\u002Foptional-skills\u002Fautonomous-ai-agents\u002Fagent-merge-conflict-arbiter\u002FSKILL.md",true,[],[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CRJRHHG68Q3XZX37TD85JB","timely","Test fixture standing in for the Timely skill (IDs, markdown dialect, workspace rule).","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Ftests\u002Ffixtures\u002Fskills\u002Ftimely\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CRJPPNS8SKWVTDP3TJ9EHG","product-price-monitor","Test fixture override of the upstream product-price-monitor skill.","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Ftests\u002Ffixtures\u002Fskills\u002Foverrides\u002Fproduct-price-monitor\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CRJKRY4QH4RAA2MKHNZT04","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Fhermes\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CRJG3JC6PRSTH3MW62KTH6","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CRJ8K3ACJYKSYDJWKJM6HV","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CRJ3Q5QP1CVBG959M3A3BM","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fthalhath2234\u002Ftimely-app\u002Fblob\u002Fdev\u002Fapps\u002Fagent\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[]]