review-go

Archcore CLI — Go Code Review

Step 1: Identify Changed Go Files

git diff --name-only HEAD -- '*.go'
git diff --cached --name-only -- '*.go'

Combine and deduplicate. Split into two lists:

• Source files: *.go excluding _test.go
• Test files: *_test.go

If no changed .go files found, ask the user which files or directories to review.

Step 2: Retrieve Project Code Quality Agreements from Archcore

Use the archcore MCP tools to load project-specific conventions that the review must check against.

1. Call list_documents with tags: ["code-review"] to find all code review agreement documents.
2. For each returned document, call get_document with its path to retrieve the full content.
3. Collect all document contents — these are the project-specific review rules that supplement the general Go review areas.

These documents contain established patterns extracted from the actual codebase (error handling conventions, naming rules, testing patterns, etc.). The reviewer agent must check changed code against these agreements.

Step 3: Pre-fetch Library Documentation via Context7 MCP

The golang-pro agent does NOT have Context7 MCP tools — fetch docs now.

1. Read go.mod for third-party dependencies.
2. Scan changed Go files for import statements. Identify which third-party libraries are used.
3. For each non-trivial library (skip stdlib, skip obvious ones): a. Call resolve-library-id with the module path (e.g., github.com/spf13/cobra) b. If resolved, call query-docs with the resolved ID and a topic query relevant to usage in the changed code
4. Limit to 3-5 most important libraries.

Step 4: Launch golang-pro Agent for Review

Use the Agent tool with subagent_type: "ivklgn:golang-pro". Pass a prompt that includes:

• The list of changed .go file paths (source and test files)
• The full text of all archcore code review documents from Step 2
• The pre-fetched library documentation from Step 3
• The review instructions below