agentleFS
Sign inStart free
XakkiXakki/ai-agents-skills/skills/code-durable-review/SKILL.md

code-durable-review

Skill6 starsChanged 3 months agoMITView on GitHub

Design or review durable jobs, leases, replay, recovery and ordered external effects. Use when an operation crosses persisted state, queues or scheduled execution. RU: очереди, повтор, восстановление.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when an operation crosses persisted state, queues, leases, journals, recovery, scheduled execution or external effects.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Durable workflows

Use when an operation crosses persisted state, queues, leases, journals, recovery, scheduled execution or external effects. Establish the operation identity, authoritative store, intended state machine, ownership/fence and authorized scope before implementation or read-only review.

Treat started, executed, terminal, external effect and durable finalization as distinct outcomes. Validate exact identity, permitted transition and active ownership before mutation; persist related state atomically when the contract requires it. A lease alone does not make an external effect exactly once. An ambiguous timeout or expired lease is not proof that the external operation did not occur and does not authorize a replay.

Use lease, replay and effects, mirrored-state and recovery and independent acceptance as applicable. Apply the actual system's transaction, clock, retry and authorization contracts; test decisive race/failure paths with synthetic fixtures and sanctioned runners. Deployment, real external calls and operator reconciliation require their own authority.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free