Agent skill

Review

by mhmzdev in mhmzdev/the-holy-quran-app

Review The Holy Qur'an app code against the project's own conventions — layering (UI → Bloc → Repo → DataProvider), bloc anatomy, Provider tier, configs tokens, class widgets, Hive typeId safety…

MITAuto-check passedDevelopment

Install Review

skills CLI
$ npx skills add mhmzdev/the-holy-quran-app --skill review -a claude-code

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

GitHub CLI
$ gh skill install mhmzdev/the-holy-quran-app review --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/mhmzdev/the-holy-quran-app.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review .claude/skills/review && 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
review
GitHub stars
889
Token cost
~907 tokens
SKILL.md length
366 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Review The Holy Qur'an app code against the project's own conventions — layering (UI → Bloc → Repo → DataProvider), bloc anatomy, Provider tier, configs tokens, class widgets, Hive typeId safety…

  • Works in 4 steps: Scope → Checklist → Report → …
  • The user says review this
  • SKILL.md covers Step 1 — Scope, Step 2 — Checklist, Step 3 — Report and Step 4 — Act (advisory), plus 1 more section
  • Calls git

What it does

Review is an agent skill from mhmzdev/the-holy-quran-app. Review The Holy Qur'an app code against the project's own conventions — layering (UI → Bloc → Repo → DataProvider), bloc anatomy, Provider tier, configs tokens, class widgets, Hive typeId safety, pinned deps, and test coverage. Use when the user says "review this", "code review", "check before merging". Produces one numbered findings report in docs/code-review/. Complements /code-review (generic bug hunting).

Its SKILL.md is about 910 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 Test coverage, Code review and Cross-platform mobile apps. It works with Flutter. The repository describes itself as: Holy Qur'an application developed via Flutter. The licence is MIT.

When your agent uses it

  • The user says review this
  • Check before merging

Example prompts

  • “an app code against the project”
  • “review this”
  • “code review”
  • “/review”

Workflow steps

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

  1. Scope
  2. Checklist
  3. Report
  4. Act (advisory)

What it can do on your machine

Read from SKILL.md and the folder at commit 33edb90. 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

Review loads about 907 tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 366 words of instructions outside code blocks.

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

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 mhmzdev/the-holy-quran-app at commit 33edb90, republished under its MIT licence (© mhmzdev). 366 words, ~907 tokens.

Download SKILL.mdSave it as .claude/skills/review/SKILL.md (or your agent's skills folder).
name
review
description
Review The Holy Qur'an app code against the project's own conventions — layering (UI → Bloc → Repo → DataProvider), bloc anatomy, Provider tier, configs tokens, class widgets, Hive typeId safety, pinned deps, and test coverage. Use when the user says "review this", "code review", "check before merging". Produces one numbered findings report in docs/code-review/. Complements /code-review (generic bug hunting).
argument-hint
optional path(s) or diff scope — defaults to the working tree diff against master

Review

A convention-aware review. Generic bug hunting belongs to /code-review; this catches what only matters in this repo (AGENTS.md, .agents/rules/, docs/conventions/). Output is one numbered report the user can act on by id.

Position: last step of /brainstorm → /grill-me → /plan → /build → **/review**.

Step 1 — Scope

  • Paths given → review those.
  • Else git diff master --name-only plus untracked files. Announce the file count and areas.
  • Nothing to diff → ask what to review; don't guess.

Step 2 — Checklist

Architecture & state

  • Layering strictly top-down (UI → Bloc → Repo → DataProvider → API/Hive)? Any widget calling a repo/provider directly?
  • Blocs: 3 part files, sealed events, Equatable states with complete props, awaited repo calls, loading → success/failed emission, registered in locator.dart and app.dart markers?
  • Providers only hold UI/app state (AppProvider may touch the app box only)?
  • Cache-first honored where data is cacheable?

Data layer

  • Model edits: new typeId for new classes, no renumbered @HiveFields, regenerated .freezed.dart/.g.dart/hive_registrar.g.dart committed, makeCollectionsUnmodifiable: false on stored lists?
  • Data provider / repo methods wrap errors as Exception('Internal … Error')?
  • Codegen dev-deps only in packages/al_quran_api?

UI conventions

  • Class widgets, App.init(context) first in build(), tokens instead of literals, withValues(alpha:), StaticAssets for assets, Screen wrapper, Arabic text in Noor?
  • Named routes via AppRoutes (except PageScreen)?

Platform / release

  • Version bumped only in pubspec.yaml when a release is intended? No new permissions? Gradle still mirrors the Flutter template? .fvmrc == CI FLUTTER_VERSION? Exact-pinned deps?

Tests

  • Every new bloc/screen has its _test.dart; success + failure + edge; no skip:/TODO/empty tests; runs offline?

Hard gates — run fvm flutter analyze and fvm flutter test; any failure is a Critical finding.

Show full SKILL.md (115 more words)Show less

Step 3 — Report

Write docs/code-review/<slug>.md with OKF frontmatter (type: Review, title, description, tags, timestamp) and stable ids, ordered severity → file → line:

markdown
# Review — <scope>  (<n> critical, <n> important, <n> suggestion)

## FINDING-01 · Critical · lib/blocs/foo/bloc.dart:42
Repo call not awaited — the failure path is swallowed. Rule: state-management/await

Print a chat summary: report path, severity counts, Critical + Important rows verbatim, Suggestions as a count. Nothing wrong → say so plainly and skip the file.

Step 4 — Act (advisory)

Via AskUserQuestion: fix criticals · fix critical+important · fix specific ids · hand to /code-review · keep the report and exit. After fixing, re-run analyze + tests and report which ids were fixed. Only touch files in scope.

What NOT to do

  • Don't duplicate /code-review's generic bug hunting.
  • Don't fix anything before the user picks an action.
  • Don't flag style you merely dislike — every finding maps to a documented rule.

© mhmzdev, MIT. 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/review of mhmzdev/the-holy-quran-app.

Open the folder on GitHubat commit 33edb90

Compare with similar skills

Review 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.

Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review this skillmhmzdev/the-holy-quran-app889—~907Automated safety check: PassMIT
Review PRhyochan/flutter_calendar_carousel860—~172Automated safety check: PassMIT
Code Review Skillawesome-skills/code-review-skill2.1k—~2.8kAutomated safety check: NotesMIT
Test Guidelinesgetsentry/sentry-dart873—~3.1kAutomated safety check: PassMIT
Grix Code Reviewaskie/grix153—~799Automated safety check: PassCustom licence
Flutter Dart Code Reviewaffaan-m/ECC275k2 repos~5.8kAutomated safety check: NotesMIT

Similar skills

  • Review PR

    hyochan/flutter_calendar_carousel

    Inspect and finish fluttercalendarcarousel pull requests by fixing valid review findings, resolving threads, diagnosing CI, and polling every five minutes until the exact head is clean.

    860 GitHub stars~172 tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • Code Review Skill

    awesome-skills/code-review-skill

    Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…

    2.1k GitHub stars~2.8k tokensUpdated 29 days ago
    DevelopmentAuto-check: notes
  • Test Guidelines

    getsentry/sentry-dart

    Official

    Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.

    873 GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Audit Grix diffs and pull requests for correctness, regressions, security, lifecycle safety, and cross-component contract consistency.

    153 GitHub stars~799 tokensUpdated today
    DevelopmentAuto-check passed
  • Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance…

    275k GitHub starsUsed in 2 repos~5.8k tokens
    MobileAuto-check: notes
  • Green Gate

    VeryGoodOpenSource/vgv-ai-flutter-plugin

    Drives a Dart or Flutter package fully green through a verify-fix-rerun loop across four gates: analyze, format, test, coverage.

    169 GitHub stars~4.7k tokensUpdated yesterday
    MobileAuto-check: notes

More from mhmzdev/the-holy-quran-app

  • Brainstorm

    mhmzdev/the-holy-quran-app

    Explore WHAT to build for The Holy Qur'an app through collaborative dialogue before any planning or code.

    889 GitHub stars~845 tokensUpdated 28 days ago
    Auto-check passed
  • Docs Gardening

    mhmzdev/the-holy-quran-app

    Audit and maintain The Holy Qur'an app's knowledge base (AGENTS.md, .agents/rules/, docs/ OKF bundle) for staleness, broken cross-links, drift from code, and OKF structural issues.

    889 GitHub stars~1.1k tokensUpdated 28 days ago
    Auto-check passed
  • Plan

    mhmzdev/the-holy-quran-app

    Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria.

    889 GitHub stars~957 tokensUpdated 28 days ago
    Auto-check passed
  • UI Design

    mhmzdev/the-holy-quran-app

    Design Flutter UI screens and widgets for The Holy Qur'an app.

    889 GitHub stars~1.2k tokensUpdated 28 days ago
    Auto-check passed
  • Grill Me

    mhmzdev/the-holy-quran-app

    Stress-test a plan, design, or idea for The Holy Qur'an app before implementation by interrogating it one question at a time — walking the decision tree, resolving dependencies, and surfacing every…

    889 GitHub stars~778 tokensUpdated 28 days ago
    Auto-check passed
  • Refine Approach

    mhmzdev/the-holy-quran-app

    Sharpen an existing brainstorm or execution plan for The Holy Qur'an app — score it for clarity, completeness, specificity, YAGNI, and scope, then improve it in place.

    889 GitHub stars~600 tokensUpdated 28 days ago
    Auto-check passed

Works with

Questions about Review

What does Review do?

Review The Holy Qur'an app code against the project's own conventions — layering (UI → Bloc → Repo → DataProvider), bloc anatomy, Provider tier, configs tokens, class widgets, Hive typeId safety…. Review is an agent skill from mhmzdev/the-holy-quran-app. Review The Holy Qur'an app code against the project's own conventions — layering (UI → Bloc → Repo → DataProvider), bloc anatomy, Provider tier, configs tokens, class widgets, Hive typeId safety, pinned deps, and test coverage.

When should I use Review?

Review fits situations like: the user says review this; check before merging.

How do I install Review in Claude Code?

Run `npx skills add mhmzdev/the-holy-quran-app --skill review -a claude-code`. Or copy the skill folder (.agents/skills/review in mhmzdev/the-holy-quran-app) into .claude/skills/review in your project. Claude Code loads it when a task matches its description.

How do I install Review in Codex?

Run `npx skills add mhmzdev/the-holy-quran-app --skill review -a codex`. Or copy the skill folder (.agents/skills/review in mhmzdev/the-holy-quran-app) into .agents/skills/review in your project. Codex loads it when a task matches its description.

Can I use Review 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 mhmzdev/the-holy-quran-app --skill review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.

What does Review need to run?

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

Does Review 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 Review 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 Review use?

Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review use?

About 907 tokens (SKILL.md is roughly 3.6k 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 Review?

Skills that share tags, products or a category with Review: Review PR (hyochan/flutter_calendar_carousel, 860 stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Test Guidelines (getsentry/sentry-dart, 873 stars) and Grix Code Review (askie/grix, 153 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review?

mhmzdev (a GitHub user) maintains it in mhmzdev/the-holy-quran-app, which has 889 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 10, 2026.

Source: mhmzdev/the-holy-quran-app on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.