The Skill directs an automatic Git commit beyond its core exercise-scaffolding purpose
Source references: 4The description promises exercise-structure creation, but the body additionally requires a `git commit` afterward. A commit permanently changes repository history, and the instruction does not require showing the diff, confirming the commit scope, or obtaining user approval.
If followed, unreviewed scaffold changes will be recorded in repository history. Any unrelated changes already staged at commit time could also be included.
The stated purpose is to scaffold lint-ready exercise directories, but the live instruction also requires `git commit`. When the skill is used for scaffolding, this would modify repository history without a workflow step to show the changes, limit the commit contents, or obtain approval. A user can prohibit automatic commits and ask the author to make committing a separate, opt-in confirmation step.
---name: scaffold-exercisesdescription: Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.---Show 3 other places
Create exercise directory structures that pass `pnpm ai-hero-cli internal lint`, then commit with `git commit`.name: scaffold-exercisesdescription: Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.---1. **Parse the plan** - extract section names, exercise names, and variant types2. **Create directories** - `mkdir -p` for each path3. **Create stub readmes** - one `readme.md` per variant folder with a title4. **Run lint** - `pnpm ai-hero-cli internal lint` to validate5. **Fix any errors** - iterate until lint passes