chore: propagate skill name frontmatter fix via uf init + replicator init#177
Merged
yvonnedevlinrh merged 1 commit intoJul 2, 2026
Conversation
…init Re-run uf init and replicator init --force to propagate the name field fix from unbound-force/unbound-force#309 and unbound-force/replicator#28. All skills now have the required name field in YAML frontmatter, making them discoverable by OpenCode skill tool. Updated pre-flight skill with name field and latest content. Added review-context skill. Updated 7 replicator-scaffolded skills with name field. Commands updated to latest scaffold versions. Ref: unbound-force/unbound-force#316 Assisted-by: OpenCode (claude-opus-4-6) Signed-off-by: Yvonne Devlin <ydevlin@redhat.com>
jflowers
approved these changes
Jul 1, 2026
jflowers
left a comment
jflowers
left a comment
Contributor
There was a problem hiding this comment.
PR Review: #177 -- chore: propagate skill name frontmatter fix
Verdict: APPROVE
All 7 skills now have the required name field matching their directory name. The new review-context skill consolidates previously duplicated context discovery logic across review-pr, review-council, and address-feedback. Command files updated to reference the new skill and incorporate soft-gate mode, STOP HERE blocks, and additional uf-init guardrails.
- Hugo build: PASS
- No CI workflows configured for this repo
- No security findings
- Constitution compliance: PASS (all 3 principles)
- No blocking issues
This review was generated by /review-pr (AI-assisted).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-run
uf initandreplicator init --forceto propagate thenamefield fix from unbound-force/unbound-force#309 andunbound-force/replicator#28. All skills now have the required
namefield in YAML frontmatter, making them discoverable by OpenCode'sskilltool.Without this fix,
/review-council,/review-pr, and/unleashfail with "Skill not found" when attempting to loadpre-flight.Changes
Skills —
namefield added (viareplicator init --force)always-on-guidance/SKILL.mdname: always-on-guidanceforge-coordination/SKILL.mdname: forge-coordinationforge-global/SKILL.mdname: forge-globallearning-systems/SKILL.mdname: learning-systemsreplicator-cli/SKILL.mdname: replicator-clisystem-design/SKILL.mdname: system-designtesting-patterns/SKILL.mdname: testing-patternsNew files (from
uf init)review-context/SKILL.mdUpdated files (from
uf init)pre-flight/SKILL.md(namefield + latest content)address-feedback.md,review-council.md,review-pr.md,uf-init.mdNo production code changes
This PR only touches agent tooling, skill files, and command files.
Verification
namefield matching directory nameContext
Issue pre-existing for other skills but discovered via unbound-force/unbound-force#309.
Scaffold sources fixed in unbound-force/unbound-force#317
and unbound-force/replicator#30.
Ref: unbound-force/unbound-force#316