When generating a skill locally with --skill-generate, the project name in SKILL.md (frontmatter description: and the H1) is always derived from the working-directory basename via generateProjectName → toTitleCase(basename(cwd)).
This is wrong when the cwd is an ephemeral/transient name. In our case the repo is checked out into git worktrees named per-instance (e.g. karachi-v2), so every generated skill leaks Reference codebase for Karachi V2 instead of the actual project name.
The skillProjectName option already exists in the codebase (packSkill.ts: const projectName = skillProjectName ?? generateProjectName(rootDirs)) and defaultAction.ts reads it from cliOptions — but it is only ever populated on the remote path (remoteAction.ts → generateProjectNameFromUrl). There is no commander .option() for it and it is not in the config schema, so local users cannot set it.
Proposal
Register a --skill-project-name <name> CLI option (and/or an output.skillProjectName config field) that flows into the existing skillProjectName plumbing. Since the wiring already exists, this should be a small change.
Workaround
Post-process SKILL.md + references/*.md after generation to replace the derived name — works, but brittle and should not be necessary given the field already exists internally.
Tested with repomix@^1.14.1.
When generating a skill locally with
--skill-generate, the project name inSKILL.md(frontmatterdescription:and the H1) is always derived from the working-directory basename viagenerateProjectName→toTitleCase(basename(cwd)).This is wrong when the cwd is an ephemeral/transient name. In our case the repo is checked out into git worktrees named per-instance (e.g.
karachi-v2), so every generated skill leaksReference codebase for Karachi V2instead of the actual project name.The
skillProjectNameoption already exists in the codebase (packSkill.ts:const projectName = skillProjectName ?? generateProjectName(rootDirs)) anddefaultAction.tsreads it fromcliOptions— but it is only ever populated on the remote path (remoteAction.ts→generateProjectNameFromUrl). There is no commander.option()for it and it is not in the config schema, so local users cannot set it.Proposal
Register a
--skill-project-name <name>CLI option (and/or anoutput.skillProjectNameconfig field) that flows into the existingskillProjectNameplumbing. Since the wiring already exists, this should be a small change.Workaround
Post-process
SKILL.md+references/*.mdafter generation to replace the derived name — works, but brittle and should not be necessary given the field already exists internally.Tested with
repomix@^1.14.1.