ai-coding-setup

Set of prompts, skills, and scripts to aid in utilizing AI coding agents in development workflows.

Prerequisites

• GitHub CLI (gh) — installed and authenticated
• Node.js (npx) — required for MCP servers
• At least one of the following AI coding tools:
  • Claude Code
  • Gemini CLI
  • Codex CLI
  • Copilot CLI

Quick Start

git clone https://github.com/rlorenzo/ai-coding-setup.git
cd ai-coding-setup
./setup

The script detects which AI tools you have installed and walks you through installing commands for each one interactively.

Windows: Run the setup script from Git Bash.

Supported Tools

Tool	Command format	Source directory	Installs to
Claude Code	Markdown (.md)	.claude/commands/	~/.claude/commands/
Gemini CLI	TOML (.toml)	.gemini/commands/	~/.gemini/commands/
Codex CLI	Agent Skills (SKILL.md)	.codex/skills/	~/.codex/skills/
Copilot CLI	Agent Skills (SKILL.md)	.copilot/skills/	~/.copilot/skills/
Shared prompts	Markdown (.md)	prompts/	~/.local/share/ai-coding-setup/prompts/

Available Commands

/commitmsg

Propose a conventional commit message for the currently staged changes. Detects ticket IDs from branch names and follows the project's recent commit style.

Usage:

• Claude Code: /commitmsg
• Gemini CLI: /commitmsg
• Codex CLI: $commitmsg
• Copilot CLI: /commitmsg

/review-pr

Process unresolved review comments on a GitHub PR, fix valid issues, ensure CI passes, and re-request review.

Usage:

• Claude Code: /review-pr [PR_NUMBER]
• Gemini CLI: /review-pr [PR_NUMBER]
• Codex CLI: $review-pr [PR_NUMBER]
• Copilot CLI: /review-pr [PR_NUMBER]

/code-refinement

Review staged files for code quality (KISS, DRY, YAGNI, Clean Code), fix linting issues, and check test coverage.

Usage:

• Claude Code: /code-refinement
• Gemini CLI: /code-refinement
• Codex CLI: $code-refinement
• Copilot CLI: /code-refinement

/code-review

Run a standalone code review on staged changes. Writes findings to agent-code-review.md.

Usage:

• Claude Code: /code-review
• Gemini CLI: /code-review
• Codex CLI: $code-review
• Copilot CLI: /code-review

Shared Prompts

The prompts/ directory contains agent-agnostic prompts consumed by the review loop scripts. These are not interactive commands — they are automation prompts read by code-review-loop and plan-review-loop.

Prompt	Role
code-review.md	Initial code reviewer
code-review-followup.md	Reviewer's follow-up review
code-review-response.md	Editor responds to review findings
code-refinement.md	Lint/refine pre-review step
plan-review.md	Initial plan reviewer
plan-review-followup.md	Plan reviewer's follow-up

How It Works

• Each AI tool has its own command format, so commands are maintained as separate source files per tool.
• The setup script copies selected commands to the appropriate user-level directory for each tool.
• Shared prompts are installed to ~/.local/share/ai-coding-setup/prompts/ and referenced by the review loop scripts.
• Installed commands are tagged with a source marker so the script can safely update them later without overwriting your custom commands that happen to share the same name.

MCP Server Configuration

The setup script can configure Model Context Protocol (MCP) servers for your AI tools. Currently supported:

Server	Package	Description
Playwright	@playwright/mcp@latest	Browser automation and web testing

MCP servers are added via each tool's mcp add CLI command at user scope.

Adding New Commands

To add a command, create the appropriate file(s) for each tool you want to support:

1. Claude Code — create .claude/commands/command-name.md (markdown with $ARGUMENTS placeholder)
2. Gemini CLI — create .gemini/commands/command-name.toml (TOML with description and prompt fields, {{args}} placeholder)
3. Codex CLI — create .codex/skills/command-name/SKILL.md (markdown with YAML front matter containing name and description)
4. Copilot CLI — create .copilot/skills/command-name/SKILL.md (same format as Codex skills)

Run ./setup again to install.

Uninstalling

Delete the command/skill from the corresponding directory:

• Claude: ~/.claude/commands/
• Gemini: ~/.gemini/commands/
• Codex: ~/.codex/skills/
• Copilot: ~/.copilot/skills/

The setup script only manages commands it originally installed.

Contributing

Running Tests

The test suite uses BATS (Bash Automated Testing System). After cloning with submodules:

git clone --recurse-submodules https://github.com/rlorenzo/ai-coding-setup.git
cd ai-coding-setup
test/run

If you already cloned without submodules:

git submodule update --init --recursive
test/run

Unit tests (test/run) cover config parsing, prompt loading, validation, and review status checks. They run in seconds and need no API keys.

Smoke Tests

Smoke tests run real AI agents against a temporary git repo to verify that CLI flags are accepted and agents can perform basic read/write tasks:

test/smoke                   # test all installed agents
test/smoke claude codex      # test specific agents
test/smoke --timeout 180     # override per-test timeout (default: 120s)

Each installed agent is tested as both editor (can it modify a file?) and reviewer (does it produce a review file?). Requires at least one AI tool installed and authenticated.

Pre-commit hooks (optional)

This repo uses pre-commit to run linters locally before each commit. Install it once and you'll get automatic checks for shell scripts (shellcheck), markdown (markdownlint), and TOML syntax.

pip install pre-commit   # or: brew install pre-commit (macOS)
pre-commit install

After that, hooks run automatically on git commit. You can also run them manually:

pre-commit run --all-files

If you skip the local setup, the same checks run in CI on your pull request.

License

MIT