agentsclimarketplace

Repokit setup

Skill DazzleML/dazzle-claude-code-config/dotclaude/skills/repokit-setup

Set up a new project using DazzleTools git-repokit-template and git-repokit-common. Creates repo, adds subtree, initializes standard structure.From its SKILL.md

Install
npx -y skills add DazzleML/dazzle-claude-code-config --skill repokit-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.3 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

RepoKit Project Setup

Full initialization of a new DazzleTools project from the git-repokit-template.

User Input

  • $ARGUMENTS: Project name, org (DazzleTools/djdarcy/DazzleNodes), description, and project type (python-pypi, python-comfyui, cpp, other).

Process

Step 1: Create GitHub Repo from Template

gh repo create <ORG>/<PROJECT_NAME> \
  --template DazzleTools/git-repokit-template \
  --public \
  --description "<description>"

The template auto-substitutes $PROJECT_NAME, $PACKAGE_NAME, $GITHUB_ORG, $CLI_COMMAND based on the repo name (via .github/workflows/setup-from-template.yml).

Step 2: Clone Locally

If the target directory already exists with content (e.g., vendor/ source):

cd <CODE_ROOT>/<PROJECT_NAME>
git clone https://github.com/<ORG>/<PROJECT_NAME>.git /tmp/<project>-template
cp -r /tmp/<project>-template/.git .
cp -r /tmp/<project>-template/.github .
cp /tmp/<project>-template/.gitignore .
cp /tmp/<project>-template/LICENSE .
cp /tmp/<project>-template/.repokit.json .
git checkout -- CONTRIBUTING.md README.md docs/.gitkeep private/claude/.gitkeep \
  private/claude/commits/commit_v0.1.0_initial-template.txt \
  tests/conftest.py tests/one-offs/README.md tests/output/.gitkeep \
  pyproject.toml

If starting fresh:

git clone https://github.com/<ORG>/<PROJECT_NAME>.git <CODE_ROOT>/<PROJECT_NAME>
cd <CODE_ROOT>/<PROJECT_NAME>

Step 3: Add git-repokit-common as Subtree

git subtree add --prefix=scripts https://github.com/DazzleTools/git-repokit-common.git main --squash
git remote add repokit-common https://github.com/DazzleTools/git-repokit-common.git

This populates scripts/ with: install-hooks.sh, paths.sh, sync-versions.py, update-version.sh, gh_issue_full.py, gh_sub_issues.py, hooks, etc.

Step 4: Install Git Hooks

bash scripts/install-hooks.sh

Step 5: Customize for Project Type

For Python (PyPI):

  • Edit pyproject.toml with project metadata
  • Ensure [tool.repokit-common] section is configured

For Python (ComfyUI):

  • Replace pyproject.toml with scripts/pyproject.toml.comfyui as starting point
  • Add ComfyUI-specific fields

For C++ (like Dazzle-Locate32):

  • The Python-specific template files need adaptation:
    • Remove or repurpose <Package>/__init__.py, __main__.py
    • Update .gitignore for C++ artifacts (*.obj, *.exe, *.pdb, *.lib, build dirs)
    • Replace pyproject.toml with a project metadata file or CMakeLists.txt
    • Update tests/ structure for C++ testing
    • Keep scripts/ subtree (hooks and tools are language-agnostic)
    • Keep private/claude/ structure (design docs, postmortems)

Step 6: Customize .gitignore

Add project-specific patterns under the # Project Specific section.

Step 7: Initialize Standard Issues

Use /github-issues-setup to create:

  • Issue #1: Roadmap (evergreen)
  • Issue #2: Notes & Quick Ideas (evergreen)

Step 8: Initial Commit

Stage the customized files and create the initial project commit. Do NOT commit until the user reviews and approves.

Directory Structure (Final)

<PROJECT>/
  .git/
  .github/              # Issue templates, workflows, dependabot
  docs/
  private/
    claude/             # Design docs, postmortems, issue drafts (gitignored)
      issues/
      commits/
  scripts/              # git-repokit-common subtree
    hooks/
    install-hooks.sh
    paths.sh
    gh_issue_full.py
    ...
  tests/
    one-offs/           # Experimental scripts
    output/             # Test output (gitignored)
  src/ or <package>/    # Project source
  vendor/               # Third-party source (if applicable)
  .gitignore
  CONTRIBUTING.md
  LICENSE
  README.md
  pyproject.toml        # or CMakeLists.txt for C++

Updating repokit-common Later

git subtree pull --prefix=scripts repokit-common main --squash

Reference

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.