fix(config): support legacy skills array

[kobecai]

Issue for this PR

Closes #22040

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

This fixes startup/config validation when opencode.json contains the older skills array format.
Before this change, a config like:

{
  "skills": [
    {
      "name": "test",
      "description": "Test skill",
      "command": "echo test"
    }
  ]
}
would fail with Invalid input: expected object, received array.
I changed config parsing so skills accepts both the current object format (paths / urls) and the legacy inline array format. I also updated skill loading
so legacy inline entries are still loaded into the skill registry instead of only avoiding the validation error.

This should fix the reported issue because the failure was happening at config schema validation time, and after that the legacy entries still need to be
surfaced as skills to preserve behavior.

### How did you verify your code works?

Ran these locally from packages/opencode:

bun test test/config/config.test.ts test/skill/skill.test.ts
bun typecheck

I also reproduced the issue first with a minimal opencode.json using the legacy skills array and confirmed it failed before the change.

### Screenshots / recordings

N/A

### Checklist

- [x] I have tested my changes locally
- [x] I have not included unrelated changes in this PR

[Arsalankhan315]

22120

…

On Sun, 12 Apr Reiwa 8 at 11:55 AM kobecai ***@***.***> wrote: Issue for this PR Closes #22040 <#22040> Type of change - Bug fix - New feature - Refactor / code improvement - Documentation What does this PR do? This fixes startup/config validation when opencode.json contains the older skills array format. Before this change, a config like: { "skills": [ { "name": "test", "description": "Test skill", "command": "echo test" } ] }would fail with Invalid input: expected object, received array.I changed config parsing so skills accepts both the current object format (paths / urls) and the legacy inline array format. I also updated skill loadingso legacy inline entries are still loaded into the skill registry instead of only avoiding the validation error. This should fix the reported issue because the failure was happening at config schema validation time, and after that the legacy entries still need to besurfaced as skills to preserve behavior. ### How did you verify your code works? Ran these locally from packages/opencode: bun test test/config/config.test.ts test/skill/skill.test.tsbun typecheck I also reproduced the issue first with a minimal opencode.json using the legacy skills array and confirmed it failed before the change. ### Screenshots / recordings N/A ### Checklist - [x] I have tested my changes locally- [x] I have not included unrelated changes in this PR ------------------------------ You can view, comment on, or merge this pull request online at: #22120 Commit Summary - 1d68eec <1d68eec> fix(config): support legacy skills array File Changes (4 files <https://github.com/anomalyco/opencode/pull/22120/files>) - *M* packages/opencode/src/config/config.ts <https://github.com/anomalyco/opencode/pull/22120/files#diff-2ca52542d251bb69bf981f39dd51de9943a6c2cb4ee53d7799c83bbf322a0891> (16) - *M* packages/opencode/src/skill/index.ts <https://github.com/anomalyco/opencode/pull/22120/files#diff-d0625ce1f1950542a87fb814cc72ccf58a3ed3a5689621f685149fdc4545b608> (55) - *M* packages/opencode/test/config/config.test.ts <https://github.com/anomalyco/opencode/pull/22120/files#diff-24f7bef0388f1a47d5b39089467e8f15077d65cbfcb18f48aaaba5b11e409b4b> (35) - *M* packages/opencode/test/skill/skill.test.ts <https://github.com/anomalyco/opencode/pull/22120/files#diff-f8486852cfc6f89192e4ee0d9aca3ea06005b47ef80aa5d3ecd0f4247b1a1e38> (33) Patch Links: - https://github.com/anomalyco/opencode/pull/22120.patch - https://github.com/anomalyco/opencode/pull/22120.diff — Reply to this email directly, view it on GitHub <#22120>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B3JG3S5MOPCLHYLEYOAAWNT4VM4X7AVCNFSM6AAAAACXVQHPICVHI2DSMVQWIX3LMV43ASLTON2WKOZUGI2DMOJTHAYDKNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>