CD dev-loop
Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open `notes/issues/`, order them by dependency, then for each issue dispatch a scoped sub-agent, review its diff, run the real gates, and commit + push to main before moving to the next. Sequential by default (one agent at a time) so changes never collide on shared files. Default scope is ALL open issues with a safety limit of 25; the user can widen the scope or raise the limit in their prompt. Pauses for the user only at genuine decision forks and before any paid generation or irreversible/outward-facing action. USE WHEN the user types `/dev-loop`, says "work through the issues", "run the dev loop", "grind the backlog", "implement all the open issues", "keep going through notes/issues until done", or after `/dev-issues` has filed a batch they now want executed. DO NOT FIRE for a single issue (just implement it), for content/video production, or when there are no open issues to execute. See body for ALSO FIRE / DO NOT FIRE / HARD INVARIANTS.
Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open notes/issues/, order…
As a process D 44/100 · Unfinished process — References files that are not bundled: ../../../notes/README.md
The same skill appears in 1 more place: ralphy
How to improve
- Shorten the description to 1024 characters.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1084 chars, limit 1024 - warning
missing-refreference to a missing file: ../../../notes/README.md - note
frontmatter-keyunknown frontmatter key "namespace" - note
edit-residuethe text marks something as outdated (lines 8, 27, 49): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 44/100
- 0Tools and files. 1 referenced file(s) missing: ../../../notes/README.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 31 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1591 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1084: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 6 headings
- +3Step-by-step instructions: 22 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.