create-new-static-website
Create New Static Website
Workflow
- Collect inputs (ask first)
- Project folder name (for
npx gitpick instructa/astro-website-starter <name>) - GitHub owner/org + repo name
- Visibility: public or private
- Whether to push immediately after init (default: yes)
- Scaffold from template
- From
~/projects, run:npx gitpick instructa/astro-website-starter <project-name>cd <project-name>
- If folder exists, ask to rename or delete (use
trash).
- Initialize git + create GitHub repo
git initgit add -Agit commit -m "feat: init"gh repo create <owner>/<repo> --public|--private --source . --remote origin --push- If user says no push: omit
--pushand inform them how to push later.
- If user says no push: omit
- Alchemy config (ask after repo creation)
- Ask if they want to configure Alchemy now.
- If yes:
cp .env.example .env- Set
ALCHEMY_PASSWORDin.env(ask for value or instruct user to set). pnpm exec alchemy login- Confirm any Cloudflare/Alchemy prompts and ensure
pnpm run devworks.
Notes
- Keep commands non-interactive when possible.
- Use
ghfor repo creation. - Don’t delete without confirmation (use
trash).
More from regenrek/agent-skills
hard-cut
Enforce a hard-cut cleanup policy: keep one canonical implementation and delete compatibility, migration, fallback, adapter, coercion, and dual-shape code. Use for pre-release or internal-draft refactors where the goal is one final shape, especially when changing schemas, contracts, persisted state, routing, configuration, feature flags, enum/value sets, or architecture.
14root-cause-finder
Performs root-cause-first debugging and review by tracing expected behavior to the first unintended side effect before changing contracts, parsing, or types. Use when debugging protocol errors, deserialization failures, null payloads, missing fields, restore or hydration issues, state-ownership bugs, unexpected requests, background mutations, or reviewing junior-created code where the visible failure may be downstream noise.
7consolidate-test-suites
Decide exactly where bug-fix test coverage belongs. Use before adding, moving, or deleting tests after a bug fix or architectural change. Select one owning layer, reuse existing canonical suites, block redundant or weakly placed tests, and remove weaker duplicates.
7git-safe-workflow
Safely inspect, stage, commit, and (only if asked) push changes made by an AI agent. Use for commit/push requests, end-of-task checkpoints, merge conflict resolution, worktree safety checks, or deciding whether to use git commit --amend.
4shellck
Run shellcheck on shell scripts after editing scripts or when debugging shell errors. Use for linting scripts in a repo (especially scripts/), catching issues like set -u with unset vars, bad subshell usage, or quoting mistakes.
3codex-analysis
Run Codex CLI for deep code analysis and second-opinion reviews. Use when the user explicitly asks for Codex analysis, Codex help, or wants a second opinion from Codex on code, architecture, or debugging questions.
3