chore: resolve merge conflict markers in convention pack files

Open
#69 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
markdown
Domain
tooling

Research direction

Start with .opencode/uf/packs/severity.md at lines 4–8, then search the other pack files for unresolved conflict markers. The issue suggests the scaffolded-by comment line may be the correct version, but check the surrounding content to choose. Done means no conflict markers remain in the affected pack files and their convention content is intact.

Written by the indexing model from the issue text.

Description

Problem

Multiple convention pack files on main contain unresolved merge conflict markers (<<<<<<< Updated upstream / >>>>>>> Stashed changes):

  • .opencode/uf/packs/severity.md:4-8
  • Other pack files likely affected

These don't break the build (packs are read by agents, not compiled) but they corrupt the convention pack content that agents consume during reviews.

Fix

Resolve the conflict markers by choosing the correct version (likely the scaffolded-by comment line).

Context

Identified during review council run on 2026-08-10. Pre-existing on main, not introduced by any PR.

Dominant language
Go
Stars
0
Forks
9
Avg merge
1d 14h
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from unbound-force/replicator

All issues in unbound-force/replicator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.