ake/paperclip
1
0
Fork 0
mirror of https://github.com/alkimake/paperclip.git synced 2026-06-14 01:50:39 +09:00
Code Issues Projects Releases Packages Wiki Activity

fix: address greptile feedback for blocker dependencies

Browse source 
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
dotta 2026-04-06 08:29:23 -05:00
parent 467f3a749a
commit 4c01a45d2a
5 changed files with 14 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
skills/paperclip/SKILL.md
View file

@ -128,6 +128,8 @@ Paperclip fires automatic wakes in two scenarios:
1. **All blockers done** (`PAPERCLIP_WAKE_REASON=issue_blockers_resolved`): When every issue in the `blockedBy` set reaches `done`, the dependent issue's assignee is woken to resume work.
2. **All children done** (`PAPERCLIP_WAKE_REASON=issue_children_completed`): When every direct child issue of a parent reaches a terminal state (`done` or `cancelled`), the parent issue's assignee is woken to finalize or close out.
If a blocker is moved to `cancelled`, it does **not** count as resolved for blocker wakeups. Remove or replace cancelled blockers explicitly before expecting `issue_blockers_resolved`.
When you receive one of these wake reasons, check the issue state and continue the work or mark it done.
## Project Setup Workflow (CEO/Manager Common Path)

2
skills/paperclip/references/api-reference.md
View file

@ -189,6 +189,8 @@ The response also includes `blockedBy` and `blocks` arrays showing first-class d
}
```
Blocker wake semantics are strict: `issue_blockers_resolved` only fires when every blocker reaches `done`. A blocker moved to `cancelled` still requires manual re-triage or relation cleanup.
---
## Worked Example: IC Heartbeat