← Tines 3BCONTENT HISTORY
WHAT CHANGED
Update to Tines 3B
Snapshot Nov 17, 2026 · 12:11 UTC · version 1.0.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Tines 3B and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Explain, test, simplify, and improve an existing workflow. Use when reviewing behavior, finding edge cases or failure points, validating sample data, or improving reliability, clarity, and performance.",
"included_files": [],
"name": "workflow-review",
"skill_md_contents": "---\nname: workflow-review\ndescription: Explain, test, simplify, and improve an existing workflow. Use when reviewing behavior, finding edge cases or failure points, validating sample data, or improving reliability, clarity, and performance.\nlicense: Apache-2.0\ncompatibility: Tines 3B\n---\n\n# Workflow review\n\nRead the workflow files and recent execution evidence before proposing changes.\n\nWhen the workflow uses named volumes or filesystem-backed state, use `workflow-volume-design` and inspect volume declarations, actual usage, and the steps on the common request path.\n\nReview the workflow as one program:\n\n1. Explain its trigger, data flow, side effects, and result.\n2. Test representative success, empty, malformed, duplicate, and dependency-failure inputs.\n3. Identify failures that can be handled locally and failures that must remain visible.\n4. Remove redundant work and simplify boundaries before adding retries or branches.\n5. Run affected steps and tests after changes.\n\nFor volume-backed workflows, check that frequent requests do not scan growing directories, mount unrelated state, or start unnecessary downstream executions. Check that every pair of writers to the same file is safe when one loses a volume conflict, that request steps report pending rather than success for writes that can still lose, that writers select bounded batches before scanning or parsing, retain input until derived changes are durable, and drain pending work under sustained input. Compare request latency, waiting executions, oldest pending age, and volume usage before and after a change.\n\nPrioritize concrete issues supported by code or execution results. Preserve intentional behavior, and do not add logging, retries, or abstractions without a specific failure they address.\n"
}SHA-256 of public snapshot: da19c9e745e648c690d5e970348f068f45cd684ce82d85ee6fb2e5d46bd48837