Returns coding standards, guardrails, and workflow for implementing a task.

WHEN TO USE:

• ALWAYS call this FIRST before writing any code

• When starting a new feature, bugfix, or refactor

• When unsure about project conventions

RETURNS:

• Detected stack (Java/Python/TypeScript/Go/Rust/etc)

• Task type classification (feature/bugfix/refactor/test/security/performance)

• MUST rules (mandatory guidelines)

• AVOID rules (anti-patterns to prevent)

• Code quality thresholds (max lines, coverage %)

• Naming conventions (classes, methods, files)

• Recommended TDD workflow

EXAMPLE: get_context({ task: "Create payment service", project_dir: "/path/to/project" })

Analyze code against coding standards with language-aware checks and heuristic fallback.

WHEN TO USE:

• After writing code, to check for issues

• During iterative development

• Before calling verify for final approval

PERFORMS ANALYSIS:

• Detects anti-patterns (empty catch, hardcoded secrets, etc.)

• Measures method/class lengths where supported

• Checks for interfaces and tests

• Calculates quality score

RETURNS:

• Score (0-100)

• CRITICAL issues (must fix)

• WARNINGS (should fix)

• Metrics (lines, methods, tests, etc.)

• PASSED/NEEDS WORK verdict

EXAMPLE: validate({ code: "public class UserService { ... }", task_type: "feature" })

Verify generated code before handoff.

WHEN TO USE:

• After generating code

• Before review, handoff, or final response

• As a final quality gate in agent workflows

WHAT IT CHECKS:

• Tests are provided (TDD compliance)

• Interfaces exist (DI compliance)

• No critical code issues

• Quality score >= 50

RETURNS:

• PASS: No blocking issues detected by configured checks

• FAIL: Issues to fix, iterate and verify again

WORKFLOW:

1. Generate code following get_context guidelines

2. Call verify({ code, tests, interfaces })

3. If FAIL: fix issues and call verify again

4. If PASS: proceed to the next workflow step

EXAMPLE: verify({ code: "class UserServiceImpl...", tests: "describe('UserService')...", interfaces: "interface UserService..." })

Search standards documentation for specific topics.

WHEN TO USE:

• Looking for specific technology guidance (kafka, docker, kubernetes)

• Need detailed information on a pattern or practice

• Exploring available standards

EXAMPLE QUERIES: "kafka", "testing", "docker", "logging", "metrics", "archunit", "flyway"

RETURNS: Up to 5 matching results with excerpts from documentation.

List all available coding standards profiles.

RETURNS: List of profiles with ID and description. Profiles include:

• java-spring-backend: Enterprise Java with Hexagonal Architecture

• nodejs: Node.js/TypeScript with Clean Architecture

• react, vue, angular: Frontend frameworks

• python: FastAPI/Django

• go, rust: Systems programming

• And more...

Use profile ID in .corbat.json or get_context will auto-detect.

Check server status, loaded profiles, and usage metrics.

RETURNS:

• Server status (OK/ERROR)

• Version

• Load time

• Profiles loaded

• Standards documents count

• Usage metrics (tool calls, most used profile)

Suggest a .corbat.json configuration for a project.

WHEN TO USE:

• Setting up Corbat for a new project

• Want to customize coding standards for a project

• Need to see available profiles and options

Analyzes the project directory and suggests optimal configuration based on detected stack.

RETURNS:

• Detected stack information

• Suggested .corbat.json content

• Available profiles list

• Setup instructions