[Mate] Add skills:override and skills:reset - #2433
Merged
wachterjohannes merged 1 commit intoAug 25, 2026
Merged
Conversation
wachterjohannes
requested review from
Nyholm,
OskarStark and
chr-hertel
as code owners
August 23, 2026 19:42
carsonbot
added
Feature
This was referenced Aug 23, 2026
wachterjohannes
force-pushed
the
eve/mate-skill-override
branch
from
August 23, 2026 20:03
5743315 to
8b54fc3
Compare
wachterjohannes
force-pushed
the
eve/mate-skill-override
branch
from
August 25, 2026 19:53
ed409fa to
4dddcc1
Compare
wachterjohannes
added a commit
that referenced
this pull request
Aug 25, 2026
…to skills:validate (wachterjohannes) This PR was squashed before being merged into the main branch. Discussion ---------- [Mate] Add skills:install --dry-run and content checks to skills:validate | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Docs? | yes | Issues | - | License | MIT Two gaps left over from #2370. Independent of #2433 and #2434. `skills:install --dry-run` answers "what would this change" before it changes it. The same reconciler runs, it just writes nothing: no generated folder is touched and `mate/extensions.php` stays as it is. The result now also carries the skills that were rebuilt, not only the newly installed ones, so a real run reports the same groups the dry run does. ```terminal $ vendor/bin/mate skills:install --dry-run Would install 1 new skill: mate-symfony-profiler Would rebuild 1 skill: mate-system-information ``` `skills:validate` so far only compared the generated folders against the record, which says nothing about whether the installed skill is any good. Two content checks are added, both warnings, so they show up under `--strict` and in CI without breaking a normal run: a Markdown link to a file that is not part of the installed skill, and a description that is very short or never says when the skill applies. That description is all an agent has when it decides whether to load the skill. Commits ------- 30f8356 [Mate] Add skills:install --dry-run and content checks to skills:validate
wachterjohannes
added a commit
that referenced
this pull request
Aug 25, 2026
…annes) This PR was squashed before being merged into the main branch. Discussion ---------- [Mate] Add skills:enable and skills:disable | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Docs? | yes | Issues | - | License | MIT Follow-up to #2433. This completes the skill lifecycle: with `skills:enable` and `skills:disable` every state transition has a command, so `mate/extensions.php` never has to be hand-edited. `skills:disable` sets `'enabled' => false` and removes the generated folders. The entry stays recorded as disabled, so the skill survives a `discover` run and can be switched back on, and an override copy under `mate/skills/` is left untouched. `skills:enable` flips it back and rebuilds. Both take the installed name or the original one, like the other `skills:*` commands. Both are also no-ops when the flag already has the requested value: they report it and return without touching the filesystem, the way `skills:reset` does. The check reads the recorded per-skill flag rather than the effective one, so a skill that is only hidden because its owning extension is disabled is still disabled properly instead of being called "already disabled". In that situation `skills:enable` warns instead of claiming success, since flipping the skill's own flag cannot make it visible. ```terminal $ vendor/bin/mate skills:disable system-information $ vendor/bin/mate skills:enable system-information ``` Commits ------- 64f9b81 [Mate] Add skills:enable and skills:disable
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.
Follow-up to #2370. That PR added the
modeaxis (managedvsoverride) tomate/extensions.php, but switching a skill tooverridestill meant hand-editing the file and copying the folder yourself.skills:overridecopies the package's version of a skill intomate/skills/<name>/and records'mode' => 'override'. The copy is taken from the declared source, so it keeps the original frontmatter name; the installedmate-name is applied at build time as for any managed skill.skills:resetswitches back tomanagedand rebuilds from the package. Your copy undermate/skills/is kept and its path reported, with--delete-copyto remove it explicitly.Both accept the installed or the original name, resolve against the recorded state so a skill stays addressable while its package is absent, and reinstall plus print the resulting row so intent and recorded facts never drift apart.