contributions-review

Contributions Review

Overview

Audit a codebase against project-specific engineering standards defined in a CONTRIBUTING_BOT.md file. The standards file lives at the project root and can contain any project-specific rules — coding style, error handling patterns, naming conventions, build requirements, linting configuration, and more.

Workflow

Step 1: Locate Standards File

Check for a standards file in the current working directory using Glob. Search in this order:

1. CONTRIBUTING_BOT.md
2. CONTRIBUTING.md
3. CONTRIBUTING (plain text)

Use the first match found. If none exist, inform the user that no contributions/standards file was found in the current directory, suggest creating a CONTRIBUTING_BOT.md, and stop.

Step 2: Determine Scope

Ask the user what scope to review using AskUserQuestion. Present three options:

1. Entire codebase — audit all source files in the repository
2. Staged changes — audit only files staged for the next git commit
3. Specific files or directories — audit only named paths

If the user has already specified a scope (e.g., "review my staged changes against the standards"), skip the question and use the stated scope.

For staged changes, run git diff --cached --name-only to get the file list.

Step 3: Spawn the Reviewer Agent

Launch the contributions-reviewer agent, providing:

• The chosen review scope (and file list if applicable)
• Clear instructions to read CONTRIBUTING_BOT.md and perform a thorough audit

The agent will read the standards document, explore the codebase within the chosen scope, and return a structured report of all violations found. Each violation includes the file path, line numbers, the standard violated, and an actionable fix description.

Step 4: Present Findings

Display the agent's violation report to the user.

If no violations were found, confirm the codebase appears compliant.

If violations were found, ask the user: "Would you like me to apply all the fixes now?"

Step 5: Apply Fixes (if requested)

If the user confirms, work through every violation in the report and apply the described fixes using Edit/Write tools. Apply all fixes at once — do not ask for approval on each individual fix.

After applying fixes, briefly confirm what was changed.

Important Notes

• Only report violations of standards explicitly documented in CONTRIBUTING_BOT.md — do not invent additional standards or suggest improvements beyond the document
• The CONTRIBUTING_BOT.md format is freeform — it can contain any project-specific engineering standards in any structure
• Skip binary files, build artifacts, lock files, and dependency directories (node_modules, target/, vendor/, .venv/) when auditing
• If a standard is ambiguous, note the ambiguity rather than silently guessing