replicant-mcp

{ "strictness": 1, "commentTypes": ["logic", "syntax", "checks"], "triggerOnUpdates": false, "ignorePatterns": "dist/**\ncoverage/**\nnode_modules/**\n*.lock\ndocs/plans/**", "instructions": "Focus on logic errors and security issues. Skip style/formatting nitpicks. Do NOT re-raise issues that were addressed in previous commits - check the diff before commenting. For design docs, focus on architectural flaws only.", "customContext": { "rules": [ "ANDROID MCP SERVER SPECIFIC CHECKS:", "", "SECURITY PATTERNS:", "- Command injection: All shell commands must use process-runner.ts patterns with parameterized execution", "- ADB safety: Flag raw shell commands that bypass adb-shell tool's safety checks", "- Path validation: Verify apkPath, module paths, and file paths are properly sanitized", "- Package names: Must follow reverse domain pattern (com.example.*)", "- Privilege escalation: Flag any sudo/root commands or privileged operations", "", "MCP PROTOCOL COMPLIANCE:", "- Tool responses: Must return ToolError (from types/errors.ts) or structured data, never raw strings", "- Error handling: Use ErrorCode constants, not magic strings or generic Error objects", "- Progressive disclosure: Large outputs (>1KB) should use cache IDs via cache-manager", "- Tool naming: Must follow 'category-action' pattern (adb-shell, gradle-build, ui-dump)", "- Schema consistency: Tool arguments must match MCP parameter schema", "", "ANDROID ECOSYSTEM AWARENESS:", "- Gradle/AGP compatibility: Check for deprecated version combinations", "- API level compatibility: Verify minSdk/targetSdk work with selected devices", "- Resource limits: Flag emulator configs exceeding typical dev machine capabilities", "- ADB version features: Check if new features require specific ADB versions", "- Dangerous permissions: Flag manifest permissions requiring user consent", "", "FEATURE BRANCHES (feature/*):", "- Logic & correctness: Verify edge cases, error conditions, and device state handling", "- Test coverage: New tools need integration tests in tool-handlers.test.ts", "- API consistency: Check patterns match existing tools in src/tools/ and src/adapters/", "- Documentation: Flag if README roadmap or rtfm docs need updates", "- Security: Command injection risks, especially in shell execution", "- Performance: Operations must scale across multiple devices/projects", "", "FIX BRANCHES (fix/*):", "- Root cause: Fix addresses actual problem, not just symptoms", "- Regression test: Should include test that would have caught the bug", "- Error code usage: Prefer specific ErrorCode over generic errors", "- Device compatibility: Test fix across different Android versions/devices", "- Scope: No drive-by changes unrelated to the fix", "", "DOCS BRANCHES (docs/*):", "- Accuracy: Must match actual tool behavior and current API signatures", "- Clarity: Understandable to Android developers new to the project", "- Code changes: FLAG AS ERROR if any .ts/.json files are modified", "- Examples: Include working examples for complex tools like ui automation", "- Sync check: README roadmap must stay in sync with actual capabilities", "", "DESIGN DOCUMENTS (docs/plans/*-design.md):", "- SKIP STYLE NITPICKS: Do not comment on formatting, token calculation rounding, type syntax spacing, etc.", "- Focus ONLY on: architectural flaws, logical errors, missing error handling, security issues", "- DO NOT re-raise issues that were addressed in previous commits", "- Maximum 3 comments per review - prioritize the most critical issues", "- If no critical issues, approve with confidence 5/5", "", "REFACTOR BRANCHES (refactor/*):", "- No behavior change: FLAG AS ERROR if tool responses or error codes change", "- Test compatibility: Ensure existing tests still pass without modification", "- MCP compliance: Don't break tool naming or response patterns", "- Import paths: Update all imports if moving files (check for .js extensions)", "- Performance: Refactors shouldn't degrade response times", "", "CHORE BRANCHES (chore/*):", "- Dependency security: Flag packages with known vulnerabilities", "- Android compatibility: Major version bumps might break device support", "- Scope: FLAG AS ERROR if src/*.ts files modified; chore is for deps/CI/tooling only", "- Build integrity: Verify changes don't break npm publish or CI pipeline", "", "UNKNOWN BRANCH PREFIX: Flag as convention violation. Must use feature/, fix/, docs/, refactor/, or chore/" ], "files": [ { "path": "CLAUDE.md", "description": "Project conventions, workflow rules, and current status" } ] } }