| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-24 | 1.8 kB | |
| v1.1.1 -- skills and agents work again outside auto mode source code.tar.gz | 2026-09-24 | 1.3 MB | |
| v1.1.1 -- skills and agents work again outside auto mode source code.zip | 2026-09-24 | 1.8 MB | |
| Totals: 3 Items | 3.1 MB | 0 | |
Skills and agents work again outside auto mode. A fix release for [#128].
Fixed
- Skills no longer abort before they start. In 1.1.0, every skill that reads your config began with a shell command Claude Code refuses to run unless it is explicitly approved. In the permission mode CCGS ships with (
default), 66 of the 74 skills stopped before doing anything — from any subdirectory of your project, and whenever Claude invoked a skill on its own, in auto mode too. Each skill now runs the config lookup as one plain command and pre-approves exactly that command in its own frontmatter. Nothing else is approved. game-designerandcreative-directorlaunch again. Both preload skills, so the aborting command stopped them at startup withShell command permission check failed … Contains expansion. They keep their preloaded skills and still have no shell access.- Config is found from any folder. Starting Claude Code inside
src/ordesign/now reads the project'sproject.yaml. /changelogworks in a repository with no commits yet.
Checked on Claude Code 2.1.277 and 2.1.281, in every permission mode, from the project root and from subdirectories.
Upgrading from 1.1.0
Overwrite .claude/skills/, .claude/hooks/yaml-helper.sh and .claude/docs/config-resolution.md. No settings or config changes. If you customised a skill or wrote your own that copied the 1.1.0 config line, update two lines in it — see UPGRADING.md → v1.1.0 → v1.1.1 (github.com).
Thanks @mamonbleau for the report and the follow-up that narrowed it down.
Full changelog: https://github.com/Donchitos/Claude-Code-Game-Studios/compare/v1.1.0...v1.1.1