agentsclimarketplace

Review workflow determinism

Skill diagrid-labs/dapr-skills/skills/review-workflow-determinism

A set of Claude Code skills to speed up the creation of Dapr Workflow applications

Install
npx -y skills add diagrid-labs/dapr-skills --skill review-workflow-determinism

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

This skill reviews Dapr Workflow code for non-determinism hazards that would cause stuck workflows on replay. Use this skill when the user asks to "review workflow for determinism", "check non-determinism in workflow", "audit Dapr workflow replay safety", or similar.

SKILL.md

3.3 KB, as published. Nobody here has run it

Review Dapr Workflow — Determinism

Overview

Scans the bodies of Dapr Workflow classes/functions for code that is not safe to run during replay. Read-only: this skill never modifies source files. Activity bodies, management endpoints, and configuration are out of scope and are covered by review-workflow-activity and review-workflow-management.

Execution Order

You MUST follow these phases in strict order. Do not load files outside the agreed scope, and do not write or edit any files.

  1. Resolve scope — Read ../shared/review-scope-prompt.md and follow it to set scope_root.
  2. Detect target — Read ../shared/review-detect-target.md and follow it to produce language and workflow_files. If workflow_files is empty, emit a single critical finding (no workflow files found) and stop.
  3. Load checklist — Based on language, read exactly one of:
  4. Scan — For each workflow file in scope, apply every rule from the loaded checklist using Grep and Read. For each match, capture file:line, the rule id, and a short evidence snippet. Confirm the match is inside workflow scope (see "Cross-reference" in each checklist) before promoting it from "Please verify" to a graded severity.
  5. Report — Format every finding using the canonical template from ../shared/review-report-format.md. Group by severity, then rule id, then file path.
  6. Show final message — Your last output is the report. Do not append a summary, follow-up question, or next-action prompt other than the ## Next steps block defined by the report format.

Prerequisites

  • Read access to the project directory.
  • No build, compile, or run step is required — this skill is fully static.

Allowed tools

Read, Grep, Glob only. The skill MUST NOT call Bash, Write, or Edit.

Rules

The full rule list, including detection patterns, severities, and suggested fixes, lives in the loaded language checklist:

Rule ids are stable across releases. New rules append; deprecated rule ids are reserved.

Show final message

The last thing you emit MUST be the report from step 5, including the ## Next steps section. The ## Next steps block should suggest:

  • Run review-workflow-activity next if any activity files exist.
  • Run review-workflow-management next if any management files exist.
  • Re-run this skill after fixes if any critical findings were reported.

Do not add any text after the report.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.