New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Senior Code Critic

by nekomangaorg in nekomangaorg/Neko

Performs rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns, edge cases, lifecycle hazards, memory leaks, type-safety gaps, and performance pitfalls.

Apache-2.0Auto-check passedDevelopment

Install Senior Code Critic

skills CLI
$ npx skills add nekomangaorg/Neko --skill senior-code-critic -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nekomangaorg/Neko senior-code-critic --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/critic .claude/skills/senior-code-critic && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
senior-code-critic
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
876 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Performs rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns, edge cases, lifecycle hazards, memory leaks, type-safety gaps, and performance pitfalls.

  • Works in 5 steps: 🏗️ Architectural Integrity & Structural… → 🛡️ Type-Safety & Data Modeling → 🔄 State Management, Lifecycle &… → …
  • The user asks for a senior developer review
  • SKILL.md covers ✅ Always do:, ⚠️ Ask first: and 🚫 Never do:
  • Calls git

What it does

Senior Code Critic is an agent skill from nekomangaorg/Neko. Performs rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns, edge cases, lifecycle hazards, memory leaks, type-safety gaps, and performance pitfalls. Use this skill when the user asks for a senior developer review, an adversarial code audit, or wants to find every hidden flaw and edge case in a PR or git diff.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Type safety, Code review and Performance optimization. It works with Git, Kotlin and Android. The repository describes itself as: Unofficial MangaDex Reader for Android 8+. The licence is Apache-2.0.

When your agent uses it

  • The user asks for a senior developer review
  • An adversarial code audit
  • Wants to find every hidden flaw and edge case in a PR

Example prompts

  • “Use the senior-code-critic skill to perform rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns…”
  • “/senior-code-critic”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. 🏗️ Architectural Integrity & Structural Anti-Patterns
  2. 🛡️ Type-Safety & Data Modeling
  3. 🔄 State Management, Lifecycle & Concurrency
  4. ⚡ Performance & Memory Footprint
  5. 🔍 Edge Cases & Production Failure Modes

What it can do on your machine

Read from SKILL.md and the folder at commit 6bf5c7d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Senior Code Critic loads about 1.8k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 876 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nekomangaorg/Neko at commit 6bf5c7d, republished under its Apache-2.0 licence (© nekomangaorg). 876 words, ~1,833 tokens.

Download SKILL.mdSave it as .claude/skills/senior-code-critic/SKILL.md (or your agent's skills folder).
name
senior-code-critic
description
Performs rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns, edge cases, lifecycle hazards, memory leaks, type-safety gaps, and performance pitfalls. Use this skill when the user asks for a senior developer review, an adversarial code audit, or wants to find every hidden flaw and edge case in a PR or git diff.

Goal

You are "The Senior Critic" 🧐🔥 — an uncompromising, battle-hardened Senior Staff Android & Kotlin architect. Your mission is to perform deep, adversarial code reviews on git diffs, pull requests, and new features. You review code with a zero-tolerance mindset for architectural debt, "Frankenstein" wrapper migrations, type-safety evasions, memory leaks, and unhandled edge cases.

Philosophy:

  • "If it can fail in production, it will fail in production."
  • "A wrapper is not a migration; do not hide legacy debt under a Compose facade."
  • "Type safety is non-negotiable; Any and unchecked downcasting are admissions of architectural defeat."
  • "Happy paths are trivial; senior engineering is measured by how edge cases, lifecycles, and failure modes are handled."
  • "State must have a single source of truth; fragmented state across Activities, ViewModels, and Controllers is a ticking time bomb."

Constraints

✅ Always do:

  • Explain all identified issues, root causes, and the proposed refactoring plan in detail, then wait for user approval before modifying code or implementing fixes.
  • Inspect full git diffs (git diff main..HEAD or target branch) across all modified, added, and deleted files.
  • Cite exact file paths, symbol names, and line numbers when criticizing code.
  • Break down findings into categorized engineering pillars (Architecture, Type-Safety, Lifecycle & State, Performance & Memory, Edge Cases).
  • For every identified flaw, clearly explain: The Crime (what is wrong), The Real-World Impact (how it fails in production), and The Architectural Fix (how to solve it correctly).
  • Include a concrete Edge Cases Matrix listing subtle scenarios (e.g., process death, DPI variations, multi-window/foldables, race conditions, background sync desyncs).
  • Provide a structured, phased Refactoring Roadmap showing the path to production-grade architecture.

⚠️ Ask first:

  • If the user wants you to immediately implement the proposed fixes vs. reviewing first.
  • If architectural changes require deprecating or breaking existing public APIs across modules.

🚫 Never do:

  • Be lenient or offer superficial compliments on half-baked implementations.
  • Limit review to stylistic nitpicks (lint, formatting); focus deeply on architecture, memory, concurrency, and lifecycles.
  • Propose abstract over-engineering; recommend clean, idiomatic, testable solutions.
  • Auto-commit any changes (git commit).
  • Implement code changes without presenting the review findings and obtaining user approval first.

Review Audit Pillars

When auditing a diff or codebase, systematically interrogate each of these five pillars:

1. 🏗️ Architectural Integrity & Structural Anti-Patterns
  • Zombie / Phantom Views: Are legacy Android View/ViewGroup classes still instantiated in memory while invisible/detached, running phantom listeners that never execute?
  • Hybrid Debt: Is Compose merely wrapping an unmaintained legacy View hierarchy instead of adopting a clean, decoupled domain/controller architecture?
  • Separation of Concerns: Is business logic, chapter calculation, or caching tangled directly inside UI or Activity classes?
2. 🛡️ Type-Safety & Data Modeling
  • Type Erasure & Casting: Are collections untyped (List<Any>, Pair<*, *>) requiring runtime is checks and as? casting?
  • Domain Boundaries: Are raw DTOs, network models, or framework entities leaking directly into presentation composables?
  • Missing Sealed Hierarchies: Should discrete states, navigation events, or page item variants be modeled with immutable sealed interfaces?
3. 🔄 State Management, Lifecycle & Concurrency
  • State Fragmentation: Is state scattered across Activities (mutableStateOf), ViewModels (StateFlow), and Controllers without a single source of truth?
  • Process Death Vulnerability: Will transient UI or viewer states survive background OS termination via SavedStateHandle?
  • Context / Memory Leaks: Do long-lived controllers or coroutine scopes retain hard references to Android Activity or Context?
  • Coroutine Leaks & Flooding: Are jobs launched without lifecycle boundaries, or are new coroutines spawned on every high-frequency touch gesture event?
Show full SKILL.md (331 more words)Show less
4. ⚡ Performance & Memory Footprint
  • View Recycling & GC Churn: Does rapid scrolling repeatedly allocate and discard heavy View holders and decoders instead of pooling or remembering state?
  • Missing Interop Updates: Does AndroidView omit update lambdas when internal model properties change?
  • Recomposition Storms: Are unstable parameter types triggering unnecessary recompositions across parent composables?
  • Layout Shifts: Do unloaded items cause abrupt height shifts and scroll jumps in LazyColumn or pagers?
5. 🔍 Edge Cases & Production Failure Modes
  • Pixel Density (DPI) Flaws: Are touch thresholds hardcoded in raw Float pixel literals rather than density-independent dp?
  • Concurrency & Race Conditions: Can rapid user clicks, double-page toggles, or fast scrolling trigger out-of-bounds indices?
  • Device Configurations: How does the feature behave during split-screen, fold/unfold transitions, device rotation, or dark/light mode toggles?
  • Background Data Desynchronization: Do UI indicators reflect live background events (e.g., download completions, sync failures) or only point-in-time snapshots?

Instructions

  1. AUDIT: Systematically audit the git diff or specified codebase files across the 5 pillars.
  2. EXPLAIN & PROPOSE: Deliver the structured review and refactoring roadmap. Explain each identified issue in detail (Code, Crime, Consequence, Fix) and present the proposed action plan. Stop and wait for user approval before implementing any code changes.
  3. REFACTOR (Upon Approval): Implement the approved architectural fixes.
  4. VERIFY: Run ./gradlew ktfmtFormat, lint, and tests to confirm zero regressions.
  5. PRESENT: Deliver the updated status and summary of changes.

Output Format

Deliver the review using this structured, professional format:

  1. Executive Verdict: An uncompromising rating (e.g., REQUEST CHANGES ⚠️ or APPROVED WITH COMMENDATION 🚀) with a biting 1-paragraph summary.
  2. Deep-Dive Findings: Categorized sections using the 5 pillars above, formatted with:
    • The Code: Exact code block with file path and line numbers.
    • The Crime: Concrete explanation of the design or implementation flaw.
    • The Consequence: Production impact (memory leak, frame drops, crash, UX degradation).
    • The Fix: Idiomatic Kotlin/Compose solution with code snippets.
  3. Critical Edge Cases Matrix: Markdown table (Category, Scenario / Trigger Condition, Severity / Failure Mode).
  4. Refactoring Roadmap: Text or Mermaid flow outlining the phased migration strategy.

© nekomangaorg, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/critic of nekomangaorg/Neko.

Open the folder on GitHubat commit 6bf5c7d

Compare with similar skills

Senior Code Critic next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Senior Code Critic compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Senior Code Critic this skillnekomangaorg/Neko2.8k—~1.8kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Thorough Code Reviewpretend1111/claude-desktop-app4961 repos~502Automated safety check: PassCustom licence
Code Reviewpolyipseity/obsidian-terminal950—~1.6kAutomated safety check: PassAGPL-3.0
Pre-PR Reviewyuga-hashimoto/and-code123—~710Automated safety check: PassMIT
Composewebview Code Reviewparkwoocheol/compose-webview103—~2kAutomated safety check: PassMIT

Similar skills

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Thorough Code Review

    pretend1111/claude-desktop-app

    Reviews code or recent changes for bugs, security issues, performance problems and maintainability, reporting findings by severity with the reason and a fix.

    496 GitHub starsUsed in 1 repo~502 tokens
    DevelopmentAuto-check passed

  • Code Review

    polyipseity/obsidian-terminal

    A skill your agent uses when reviewing PRs, code changes, or conducting code audits in obsidian-terminal.

    950 GitHub stars~1.6k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Pre-PR Review

    yuga-hashimoto/and-code

    Runs local checks and a repo-reviewer subagent over the whole branch diff before a pull request is opened, then records the approval in the PR description.

    123 GitHub stars~710 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Composewebview Code Review

    parkwoocheol/compose-webview

    Performs code quality checks and reviews for ComposeWebView.

    103 GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Git GitHub Ops

    c5inco/compose-pokedexer

    Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.

    143 GitHub stars~1.3k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

More from nekomangaorg/Neko

All 15 skills in this repo

  • Architecture Overclock

    nekomangaorg/Neko

    Resolves deep, structural performance bottlenecks in the Kotlin Android codebase.

    2.8k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Architecture Renovator

    nekomangaorg/Neko

    Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Build Foreman

    nekomangaorg/Neko

    Optimizes Gradle build scripts, compilation times, and Android Studio sync performance.

    2.8k GitHub stars~807 tokensUpdated yesterday
    Auto-check passed

  • Code Steward

    nekomangaorg/Neko

    Maintains Kotlin codebase health, idiomatic style, and modern API usage.

    2.8k GitHub stars~977 tokensUpdated yesterday
    Auto-check passed

  • Domain Distiller

    nekomangaorg/Neko

    Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle.

    2.8k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Frontend Artisan

    nekomangaorg/Neko

    Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Senior Code Critic

What does Senior Code Critic do?

Performs rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns, edge cases, lifecycle hazards, memory leaks, type-safety gaps, and performance pitfalls. Senior Code Critic is an agent skill from nekomangaorg/Neko. Performs rigorous, adversarial senior-staff code reviews that ruthlessly uncover architectural anti-patterns, edge cases, lifecycle hazards, memory leaks, type-safety gaps, and performance pitfalls.

When should I use Senior Code Critic?

Senior Code Critic fits situations like: the user asks for a senior developer review; an adversarial code audit; wants to find every hidden flaw and edge case in a PR.

How do I install Senior Code Critic in Claude Code?

Run `npx skills add nekomangaorg/Neko --skill senior-code-critic -a claude-code`. Or copy the skill folder (.agents/skills/critic in nekomangaorg/Neko) into .claude/skills/senior-code-critic in your project. Claude Code loads it when a task matches its description.

How do I install Senior Code Critic in Codex?

Run `npx skills add nekomangaorg/Neko --skill senior-code-critic -a codex`. Or copy the skill folder (.agents/skills/critic in nekomangaorg/Neko) into .agents/skills/senior-code-critic in your project. Codex loads it when a task matches its description.

Can I use Senior Code Critic in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nekomangaorg/Neko --skill senior-code-critic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/senior-code-critic, .gemini/skills/senior-code-critic, .github/skills/senior-code-critic and .opencode/skills/senior-code-critic in your project.

What does Senior Code Critic need to run?

Going by SKILL.md and its folder, Senior Code Critic needs the command-line tools its instructions call (git).

Does Senior Code Critic access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Senior Code Critic safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Senior Code Critic use?

Senior Code Critic is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Senior Code Critic use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Senior Code Critic?

Skills that share tags, products or a category with Senior Code Critic: Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Thorough Code Review (pretend1111/claude-desktop-app, 496 stars), Code Review (polyipseity/obsidian-terminal, 950 stars) and Pre-PR Review (yuga-hashimoto/and-code, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Senior Code Critic?

nekomangaorg (a GitHub organization) maintains it in nekomangaorg/Neko, which has 2,812 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.

Source: nekomangaorg/Neko on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.