JustasMonkev

Use when asked to audit docs, review docs accuracy, or validate documentation claims against actual code, commands, APIs, configs, and diagrams.

Use when asked to grade, evaluate, assess, score, or review an agent skill's quality.

Use when asked to monitor an upstream repository for new commits, releases, merged PRs, or breaking changes affecting a local fork or wrapper.

Use when asked to find similar projects, existing tools, prior art, libraries, or whether something already exists before building.

Use when asked to find security vulnerabilities, run a security scan, review security fixes, or assess a repository for exploitable issues.

Use when asked to update dependencies, upgrade packages, avoid deprecated packages, or fix issues after a dependency update.

Verify the latest official framework documentation before implementing or modifying features. Use when requests involve framework or library behavior, new feature implementation, upgrades, deprecations, API usage, or configuration changes where outdated guidance could cause regressions. Do NOT use for trivial CSS changes, general algorithm questions, or when the user explicitly states they have already checked docs.

Review pull requests, commits, branch ranges, or working-tree changes for the JustasMonkev/open-code-review repository. Use when asked to code review changes touching the Open Code Review Go CLI, review agent, diff parsing, rule matching, LLM clients, config/env handling, session viewer, telemetry, npm wrapper, release scripts, docs, or CI. Produces findings-first review output grounded in changed lines, project conventions, and deterministic validation.

Clone and inspect external GitHub repositories in a reusable local cache at ~/explore/repos. Use when asked to explore, inspect, investigate, compare, review, or answer questions about a repository that is not already in the current workspace, especially when the request names a GitHub owner/repo or repository URL.

Verify the latest official framework documentation before implementing or modifying features. Use when requests involve framework or library behavior, new feature implementation, upgrades, deprecations, API usage, or configuration changes where outdated guidance could cause regressions. Do NOT use for trivial CSS changes, general algorithm questions, or when the user explicitly states they have already checked docs.

Navigate apps via appium-recorder CLI with minimal round-trips. Prefer deterministic paths (direct URL navigation) before selector discovery.

Teach one concrete technical command, file, error, config, repo behavior, or code mechanism through an evidence-grounded worked example, inline. Use when the user asks to understand, learn, explain, or be walked through one specific technical thing. Do not use for broad curricula, saved lesson files, multi-topic training, or when a more specific debugging, framework-docs, security, document-editing, or product-design skill should lead.