chore: run uf init to sync scaffold with uf. namespace prefix
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- markdown
- Domain
- tooling
Research direction
Read the listed .opencode/commands/ files and identify the repository’s unbound-force init entry point or /uf-init command. Run it to sync the scaffold, then check that the old command names are gone, the uf.-prefixed names and updated skills, packs, and agent files are present, and make check passes. Done means the changes are committed on a branch and merged before the batch-fix work begins.
Written by the indexing model from the issue text.
Description
Summary
Run unbound-force init (or /uf-init) in the replicator repo to pull the latest scaffold assets from unbound-force. This syncs the command files to the uf. namespace prefix introduced by unbound-force/unbound-force#304.
Current State
The replicator repo still has unprefixed uf-owned command files:
.opencode/commands/address-feedback.md
.opencode/commands/agent-brief.md
.opencode/commands/cobalt-crush.md
.opencode/commands/constitution-check.md
.opencode/commands/finale.md
.opencode/commands/review-council.md
.opencode/commands/review-pr.md
.opencode/commands/triage-issue.md
.opencode/commands/uf-init.md
.opencode/commands/unleash.md
Expected After uf init
These files should be renamed to the uf. namespace:
| Old name | New name |
|---|---|
address-feedback.md |
uf.address-feedback.md |
agent-brief.md |
uf.agent-brief.md |
cobalt-crush.md |
uf.cobalt-crush.md |
constitution-check.md |
uf.constitution-check.md |
finale.md |
uf.finale.md |
review-council.md |
uf.review-council.md |
review-pr.md |
uf.review-pr.md |
triage-issue.md |
uf.triage-issue.md |
uf-init.md |
uf.init.md |
unleash.md |
uf.unleash.md |
The content of these files will also be updated with all fixes merged into the upstream scaffold (AskUserQuestion gates, compression guards, STOP gate placement, etc.).
Skills (pre-flight, speckit-workflow), convention packs (severity.md), and agent files (cobalt-crush-dev.md) will also be updated.
Why This Must Happen First
Issues #46-#51 target files in internal/agentkit/content/ for compression hardening. The batch-fix script uses /opsx-propose, /unleash, and /finale — after this chore, those commands will be /opsx-propose, /uf.unleash, and /uf.finale. The script and issue descriptions need to reference the correct command names.
Acceptance Criteria
- Old unprefixed command files removed
- New
uf.-prefixed command files present - Skills and packs updated to latest scaffold versions
-
make checkpasses (or equivalent CI checks) - Committed on a branch, PR created and merged before batch-fix runs
- Dominant language
- Go
- Stars
- 0
- Forks
- 9
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from unbound-force/replicator
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#95 ·
Maintainers usually reply within 1 day
-
bug github_actions
Difficulty 2/5 Under an hour Newbie friendliness 80/100
unbound-force/replicator#89 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#85 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
unbound-force/replicator#77 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#63 ·
Maintainers usually reply within 1 day
All issues in unbound-force/replicator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day