android code review

Engineering Community

Skill notes

Arguments

Argument · Description · Example --branch <name> · Specify the branch to review · --branch feature/payment --base <branch> · Base branch for comparison (default: develop) · --base main --file <path> · Review a single file · --file app/src/.../LoginViewModel.kt --focus <dimension> · Focus on a specific review dimension · --focus performance

Step 1 — Fetch Code Changes

Retrieve the code to review based on the provided arguments: Note: this reviews committed changes only. Uncommitted staged/unstaged changes are not included. Use --base to change the base branch (default: develop).

Step 2 — Analyze

Using the dimensions and checklists defined below, analyze each changed file for: Architecture & design correctness Kotlin code quality Android platform best practices Performance issues

Step 3 — Generate Review Report

Output the report following the Standard Output Format defined below.

Step 4 — Save Report (Optional)

If --output <path> was specified, use the Write tool to save the full report markdown to that path.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@meganz · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview android-code-review.preview
# Standard Output Format

All review reports must strictly follow this format: ````markdown # PR Code Review Report

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.