What is review-story?

A command for reviewing the testing design of a development story before it is accepted. It checks whether the story's requirements are covered by tests and creates a review decision.

Reviewing completed development stories, mapping requirements to tests, finding coverage gaps, and recording a pass, concern, or failure decision.

It exposes missing test coverage and increases review depth for changes such as security, payment, or large code updates.

How julianobarbosa/azure-finops-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to julianobarbosa/azure-finops-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/julianobarbosa/azure-finops-mcp-server/main/.claude/commands/BMad/tasks/review-story.md

Clone the repo

git clone --depth 1 https://github.com/julianobarbosa/azure-finops-mcp-server

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/review-story/github.svg)](https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/review-story)

Your own site

<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/review-story"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/review-story/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/review-story"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/review-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,299 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02299
Opus 5	$0.00000	$0.01149
Sonnet 5	$0.00000	$0.00460
Haiku 4.5	$0.00000	$0.00230

Measured 12d ago against content hash 11e3f0facaf2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

review-story scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

review-story — 100% identical, 2 lines differ

.claude/commands/BMad/tasks/review-story.md · 321 lines

How it starts

The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/review-story Task

When this command is used, execute the following task:

review-story

Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.

Inputs

required:
  - story_id: '{epic}.{story}' # e.g., "1.3"
  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
  - story_title: '{title}' # If missing, derive from story file H1
  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)

Prerequisites

Story status must be "Review"
Developer has completed all tasks and updated the File List
All automated tests are passing

Review Process - Adaptive Test Architecture

1. Risk Assessment (Determines Review Depth)

Auto-escalate to deep review when:

Auth/payment/security files touched
No tests added to story
Diff > 500 lines
Previous gate was FAIL/CONCERNS
Story has > 5 acceptance criteria

2. Comprehensive Analysis

A. Requirements Traceability

Map each acceptance criteria to its validating tests (document mapping with Given-When-Then, not test code)
Identify coverage gaps
Verify all requirements have corresponding test cases

B. Code Quality Review

Architecture and design patterns
Refactoring opportunities (and perform them)
Code duplication or inefficiencies
Performance optimizations
Security vulnerabilities
Best practices adherence

C. Test Architecture Assessment

Test coverage adequacy at appropriate levels
Test level appropriateness (what should be unit vs integration vs e2e)
Test design quality and maintainability
Test data management strategy
Mock/stub usage appropriateness
Edge case and error scenario coverage
Test execution time and reliability

D. Non-Functional Requirements (NFRs)

Security: Authentication, authorization, data protection
Performance: Response times, resource usage
Reliability: Error handling, recovery mechanisms
Maintainability: Code clarity, documentation

Read the full file on GitHub · 321 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 321 lines · 0 tokens per session scan A 11e3f0facaf2

Subscribe to this mod's changes

review-story is a command published in the GitHub repository julianobarbosa/azure-finops-mcp-server (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,299 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

azure-finops-mcp-server: Command for Claude Code