Issue delivery loop
CLI to pull Agent Skills anywhere, anytime
npx -y skills add echohello-dev/skillet --skill issue-delivery-loopAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Use when executing GitHub issues end-to-end and you need a consistent flow for scoping, verification, merge readiness, and closure.
SKILL.md
1.3 KB, 223 tokens by cl100k_base, as published. Nobody here has run it
Issue Delivery Loop
Use this skill to keep issue execution predictable, reviewable, and complete.
When to Use
- You are implementing or fixing behavior tied to one or more issues.
- The request requires verified outcomes, not just code changes.
- You need to keep PR and issue status synchronized.
Core Flow
-
Scope the issue
- Capture objective, acceptance criteria, and dependencies.
- Decide whether the issue can be completed independently.
-
Deliver in a dedicated branch
- Keep changes scoped to the issue.
- Avoid mixing unrelated work.
-
Verify before merge
- Run project-standard validation commands.
- Confirm expected behavior and no regressions.
-
Close the feedback loop
- Open a linked PR with concise verification evidence.
- Merge only after required checks pass.
- Confirm the issue is closed and traceable to the merged work.
Guardrails
- Do not claim completion without fresh verification evidence.
- Keep progress visible with short milestone updates.
- Prefer clear, factual summaries over narrative detail.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.