Generate or repair a project's .gitignore. Composes the baseline must-ignore set (the single source of truth in baseline-ignores.json) with optional gitignore.io enrichment, and merges add-only so existing entries are never lost. Use when a repo has no .gitignore, when the commit-leak guard reports a gap, or when onboarding a new stack. Trigger: "set up gitignore", "fix my gitignore", "ignore node_modules/secrets", "gitignore for <stack>".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
This skill produces a correct .gitignore for the current project. It runs in main context (Article II). It never blocks a commit — enforcement is the gitignore_leak_guard hook's job; this skill repairs what the guard flags.
The canonical baseline must-ignore set lives at .claude/skills/gitignore/baseline-ignores.json (entries spanning secret, state, and tooling categories). Consumer-specific additions live in project.json → gitignore.extra_must_ignore. The same set is read by the install/init merge and by the gitignore_leak_guard hook, so the three never drift.
baseline-ignores.json and the consumer extras from project.json → gitignore.extra_must_ignore. These are mandatory — they MUST end up in the final .gitignore.GET https://www.toptal.com/developers/gitignore/api/listGET https://www.toptal.com/developers/gitignore/api/<type1,type2,...> (e.g. node,macos,visualstudiocode) → plain-text .gitignore body.
Use WebFetch. This is enrichment only..gitignore already exists, never overwrite or reorder it. Append only the lines (baseline + enrichment) that are not already present, preserving the existing content byte-for-byte. If none exists, create it from the baseline (+ enrichment)..gitignore entries is forbidden.gitignore_leak_guard) reads the same set; keeping baseline-ignores.json current keeps generation and enforcement in lockstep.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
The English summary is being prepared. Showing the original description.
Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.
The English summary is being prepared. Showing the original description.
PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.
The English summary is being prepared. Showing the original description.
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after `/intake` when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at `docs/brd/<slug>.md`.
The English summary is being prepared. Showing the original description.
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.
The English summary is being prepared. Showing the original description.
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
The English summary is being prepared. Showing the original description.