repo-bootstraplisted

Set up a repository to use Claude Code plugins from the portka-tools marketplace, especially for Claude Code on the web. Use when the user wants to onboard a repo to a marketplace/plugin, enable a plugin in a specific repo, scaffold .claude/settings.json (+ optional CI) for ephemeral web sessions, or asks for the Portka standard / to standardize how Claude works in a repo.
cportka/claude-plugins · ★ 0 · AI & Automation · score 70

Install: claude install-skill cportka/claude-plugins

# Repo Bootstrap Make marketplace plugins load in a repo — including **web sessions**, where `~/.claude` doesn't persist. The durable mechanism is a committed **`.claude/settings.json`** that declares the marketplace and enables the plugins. This skill writes it (and optional CI). Local-CLI-only use doesn't need this: `/plugin marketplace add cportka/claude-plugins` then `/plugin install <name>@portka-tools` persists in `~/.claude` across all local repos. ## Steps 1. **Ask** which plugins to enable (e.g. `video-bug-analyzer`), whether to add CI, and whether to apply the **Portka standard setup** (`--portka-standard`, below). Default marketplace: `portka-tools` (`cportka/claude-plugins`). 2. **Run** the script: ``` ${CLAUDE_PLUGIN_ROOT}/skills/repo-bootstrap/scripts/bootstrap-repo.sh \ --plugin <name> [--plugin <name> ...] [--ci] [--dir <repo-root>] [--dry-run] [--auto-update] \ [--portka-standard] [--scope user|project|both] [--print-only] ``` `--dry-run` previews without writing (and states the real outcome per file). `--auto-update` is catalog-only on third-party marketplaces — `claude plugin update <name>@<marketplace>` is the reliable refresh (see `--help`). Merges never clobber other keys; invalid existing JSON stops the run rather than risk data loss. 3. **Review + commit** `.claude/settings.json` (and any workflow). It only takes effect once committed — web sessions clone the repo fresh and read it at session start. Resultin