init-repo
Initializing Project
Scaffold a new project repository optimized for agentic development from a problem description -- or just set up ops tooling (git, precommits, gitignore, licensing, etc.) for an existing or empty project.
Quick Start
When invoked, follow the workflow below sequentially. After detecting the environment in Step 0, gather all preferences in a single Phase 1 intake form before executing any steps. This minimizes back-and-forth turns.
State Variables
Track these variables throughout the entire workflow. Once set, use the stored value -- never hardcode a branch name like main or master.
| Variable | Set in | Description |
|---|---|---|
{DEFAULT_BRANCH} |
Step 0 (detected) or Phase 1 | The repository's default branch name (e.g., main, master, develop). Every later step that references a branch MUST use this variable. |
{PROJECT_KIND} |
Phase 1 | Whether the project is an Application (binary/executable) or Library (reusable code). |
{INSTALLED_DEPS} |
Step 5.5 | List of recommended dependencies the user chose to install. Used in README (Step 10), CLAUDE.md (Step 11), and Summary (Step 12). |
{LLVM_COV} |
Phase 1 | Whether LLVM coverage is enabled (yes/no). Only set for Rust projects with GitHub Actions CI. |
{COV_THRESHOLD} |
Phase 1 | Minimum coverage percentage (e.g., 80), or empty if no threshold enforced. |
More from nathan13888/nice-skills
doc-n-fix
Processes PR review feedback into a prioritized checklist, documents it to a
7wtf
Quick situational awareness for the current git branch. Summarizes what a
6send-it
Push feature branch and create a GitHub PR with structured title and
6explore
Strategic discovery of a project's capabilities from a solutions architect
6check
Verifies the agent's current work against a specific question by analyzing
6sus
Finds suspicious, architecturally problematic, or high-impact maintainability
6