Notes & Quick Ideas
Quick notes, small bugs, and ideas that don't warrant their own issue yet.
Ideas
- Consider a
repokit doctor command that checks a project's health (hooks installed, gitignore correct, worktrees configured, private/ initialized)
repokit status to show branch topology, worktree layout, and private content state at a glance- Template inheritance -- allow project-specific templates to extend base templates rather than replacing them
repokit sync-private to push/pull the private nested repo to/from a backup remote- Pre-built
.claude/ directory structure in templates (skills, commands, agents scaffolding)
Quick bugs / observations
git-repokit-template CONTRIBUTING.md says "submodule" but the actual approach is subtree -- docs inconsistency.repokit.json in this repo still has "name": "my-project" as placeholderrevisions/ directory exists on disk but only has __pycache__/ -- unclear if it's used
Notes from ecosystem survey
Notes & Quick Ideas
Quick notes, small bugs, and ideas that don't warrant their own issue yet.
Ideas
repokit doctorcommand that checks a project's health (hooks installed, gitignore correct, worktrees configured, private/ initialized)repokit statusto show branch topology, worktree layout, and private content state at a glancerepokit sync-privateto push/pull the private nested repo to/from a backup remote.claude/directory structure in templates (skills, commands, agents scaffolding)Quick bugs / observations
git-repokit-templateCONTRIBUTING.md says "submodule" but the actual approach is subtree -- docs inconsistency.repokit.jsonin this repo still has"name": "my-project"as placeholderrevisions/directory exists on disk but only has__pycache__/-- unclear if it's usedNotes from ecosystem survey
git-repokit-commonandgit-repokit-templateare not yet integrated into therepokitCLI tool itselfdazzle-privateatC:\code\dazzle-private\demonstrates the standalone private repo pattern we want to adopt