audit-infra
Infrastructure-first security audit — secrets, supply chain, CI/CD, LLM/skill security, OWASP, STRIDE. Complements /audit-solana (program-level)
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them)
> /plugin marketplace add solanabr/solana-ai-kit > /plugin install solana-ai-kit@stbr
How it fires
How this command gets triggered: by you, by Claude, or both.
/commit-claude-configContext preview
What this command does when you run it.
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them)
description: "Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them)"
You are opting this project **into** version-controlling its Solana AI Kit config. By default `install.sh` gitignores the kit (`.claude/`, `CLAUDE.md`, `.mcp.json`, `.gitmodules`) so it stays out of the user's repo. This command reverses that: it removes the config block from `.gitignore`, stages those files, and commits them — so the config travels with the repo (team setup, reproducible config).
The `ext/` skill submodules stay gitignored (they're upstream content, re-fetched via `git submodule update`, not vendored). Only `.gitmodules` is tracked, so the submodule list ships and a `--recurse-submodules` clone can repopulate them.
if ! git rev-parse --is-inside-work-tree >/dev/null 2>&1; then echo "✗ Not a git repository. Run 'git init' first, then re-run /commit-claude-config." exit 1 fi # Which config dir is installed? if [ -d .claude ]; then CONFIG_DIR=.claude elif [ -d .agents ]; then CONFIG_DIR=.agents else echo "✗ No .claude/ or .agents/ found — nothing to commit."; exit 1 fi echo "▸ Config dir: $CONFIG_DIR/"
Remove the `# >>> solana-ai-kit config … <<<` block from `.gitignore` (leaves the `ext/` and local-only sections untouched). Portable across GNU/BSD sed via a temp file.
if [ -f .gitignore ] && grep -qF ">>> solana-ai-kit config" .gitignore; then
sed '/# >>> solana-ai-kit config/,/# <<< solana-ai-kit config <<</d' .gitignore > .gitignore.tmp \
&& mv .gitignore.tmp .gitignore
echo "✓ Removed the config block from .gitignore (ext/ + local-only stay ignored)"
else
echo "ℹ config block already absent from .gitignore — continuing"
fi`ext/` is still gitignored, so `git add "$CONFIG_DIR"` records your agents/commands/rules/skills/settings but NOT the 18 upstream submodule trees.
git add .gitignore 2>/dev/null || true for p in .gitmodules CLAUDE.md .mcp.json "$CONFIG_DIR"; do [ -e "$p" ] && git add "$p" done echo "" echo "Staged:" git diff --cached --name-status
if git diff --cached --quiet; then echo "ℹ Nothing to commit — kit config is already tracked and up to date." exit 0 fi git commit -m "chore: track Solana AI Kit config" echo "" echo "✓ Committed. The kit config now travels with this repo."
Production-ready Claude Code configuration for full-stack Solana development. Combines best practices from multiple sources into an agent-optimized, token-efficient config you can install and adapt to your specific project.
Repo: solanabr/solana-ai-kit
Infrastructure-first security audit — secrets, supply chain, CI/CD, LLM/skill security, OWASP, STRIDE. Complements /audit-solana (program-level)
Benchmark CU usage and compare against baseline for regression detection