Skip to content
Back to skills

Start

ASecurity

EXPLICIT-INVOCATION ONLY — trigger only when the user types /start. Initializes a new project with stack-aware CLAUDE.md, .bravros/config.json, .gitignore, and base structure. Do NOT trigger on natural-language phrases like init or setup without the slash.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentspythongobashreactnextjsnodenodejsgitdatabase

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add bravros/bravros --skill start --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Start?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Start
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bravros-start/badge)](https://www.skillsdirectory.com/skills/bravros-start)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: start
core: true
description: EXPLICIT-INVOCATION ONLY — trigger only when the user types /start. Initializes a new project with stack-aware CLAUDE.md, .bravros/config.json, .gitignore, and base structure. Do NOT trigger on natural-language phrases like init or setup without the slash.
---

# /start — initialize or refresh project workflow files

Requires a git repo. **Update mode** if `.githooks/` or `.github/workflows/claude.yml`
exists; else **Init mode**. Report the detected mode. Init: `cp -n` everywhere, never
overwrite. Update: NEVER touch an existing CLAUDE.md; refresh `claude.yml` only.

## Steps

1. **Detect stack** from project markers (composer.json+laravel/framework → laravel; package.json "next" → nextjs; "react-native"/"expo" → expo; other package.json → nodejs; go.mod → go; requirements.txt/pyproject.toml → python; else generic). **Cache it in `.bravros/config.json`** (`stack` object) — that file is the project's stack cache; later sessions and skills read it instead of re-detecting.
2. **CLAUDE.md** (Init only). Laravel fast path: `cp -n ~/.agent_config/templates/CLAUDE.md CLAUDE.md`, fill its placeholders — do not modify that template. Other stacks: generate from `references/claudemd-templates.md`. Never use the Laravel template as a base for non-Laravel projects.
3. **sync-db.sh** (relational-DB projects only): `cp -n ~/.agent_config/templates/sync-db.sh` + `.db-sync.env.example`, `chmod +x`, `mkdir -p database/backups`. Non-Laravel: swap the post-restore command (Prisma → `npx prisma migrate deploy`, Drizzle → `npx drizzle-kit push`). Gitignore `.db-sync.env` and `database/backups/`.
4. **Hooks + planning dir**: `git config core.hooksPath .githooks`; `mkdir -p .planning`. **Update mode — don't clobber graphify's hooks:** if the repo has `.graphify` or `graphify-out/graph.json`, the `post-{merge,commit,checkout}` slots are graphify refresh delegators — preserve them.
5. **`.bravros/config.json` staging branch.** A legacy `.bravros.yml`/`.sbravros.yml` is migrated to `.bravros/config.json` automatically by any `bravros` verb — never `git mv` it. If `.bravros/config.json` has no `staging_branch`, announce (below), then ask_question: "What is your staging/integration branch name? (say none for a main-only repo)" (default `homolog`). A named branch → write `{"staging_branch": "<answer>"}` to `.bravros/config.json`. No staging branch → run `bravros police direct-main on` instead (writes `.bravros/config.json` with `police.direct_main: true` so `main` isn't gated) and do not set `staging_branch`.
6. **Homolog branch before workflows.** If neither `refs/heads/homolog` nor `origin/homolog` exists: `git checkout -b homolog && git push -u origin homolog` (no origin is fine), then switch back.
7. **GitHub Actions** (only for homolog→main repos): write `claude.yml` + `tests.yml` per `references/github-workflows.md` — its GitHub gotchas are hard-won, do not deviate. Starter-kit workflow cleanup: fresh-init repos (≤1 commit) remove other workflows automatically; brownfield repos require explicit ask_question approval — never delete silently.
8. **graphify section**: if a graph exists and CLAUDE.md lacks a `## graphify` heading, append the section from `~/.agent_config/skills/graphify-this-project/references/claude-md-section.md`, filling real counts/labels — never ship placeholders.
9. **Report** created/skipped files and next steps. Don't commit automatically — the user reviews first.

<!-- announce-template: "Aguardando o nome do ramo de homologação para configurar o projeto. Ramo {BRANCH}, projeto {PROJECT}." -->
```bash
bash ~/.agent_config/scripts/announce.sh --force "Aguardando o nome do ramo de homologação para configurar o projeto. Ramo $(git branch --show-current), projeto $(basename "$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")")." studio || true
```

Use $ARGUMENTS for any additional context.

Files in this skill

  • SKILL.md3.5 KB
  • references/claudemd-templates.md2.3 KB
  • references/github-workflows.md3.7 KB
  • skill.yaml4.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.