# Reported issues for coding-standards

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [coding-standards](/mcp/coding-standards).

## Most discussed

### Add IDE-specific integration recipes

Add verified recipes for common MCP hosts with version/date, config path, verification command, and known limitations.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/42) · 2026-07-03 · open · 0 comments

### Design policy pack extension model

Design how teams can add reusable policy packs without changing core profiles. Include versioning, validation, discovery, and compatibility rules.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/41) · 2026-07-03 · open · 0 comments

### Design enterprise profile packs

Define enterprise profile pack structure for stricter regulated environments, including auditability, security, testing, observability, and release policy expectations.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/40) · 2026-07-03 · open · 0 comments

### Add multi-agent workflow examples

Create runnable examples for Corbat-guided planner, implementer, reviewer, security, and release agent workflows. Keep Corbat as policy engine rather than orchestration runtime.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/39) · 2026-07-03 · open · 0 comments

### Add Go analyzer backend

Implement a Go-specific analyzer backend behind the LanguageAnalyzer interface. Scope should include function spans, interfaces, imports, table-driven tests, error handling patterns, and focused tests.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/38) · 2026-07-03 · open · 0 comments

### Add Java analyzer backend

Implement a Java-specific analyzer backend behind the LanguageAnalyzer interface. Scope should include class/method spans, interfaces, imports, tests, exception patterns, and focused tests.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/37) · 2026-07-03 · open · 0 comments

### Add Python analyzer backend

Implement a Python-specific analyzer backend behind the LanguageAnalyzer interface. Scope should include function/class spans, imports, tests, common unsafe patterns, and focused tests.

[Read the thread](https://github.com/corbat-tech/coding-standards-mcp/issues/36) · 2026-07-03 · open · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/corbat-tech/coding-standards-mcp/issues).