Use after completing meaningful work — features merged, architectural decisions made, blockers resolved, or significant discoveries — to write project updates in GitHub Projects
From nightshiftnpx claudepluginhub klefix/nightshift --plugin nightshiftThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Write project updates to GitHub Projects after meaningful milestones. Decide autonomously what's "worthy" of an update. Write for a PM or stakeholder checking in.
Worthy of an update:
NOT worthy:
# Recent merged PRs
gh pr list --state merged --limit 10
# Recently closed issues
gh issue list --state closed --limit 10
# Recent commits
git log --oneline -20
# Check for new ADRs
ls docs/adr/ 2>/dev/null
Batch related work into one update. Don't write one update per PR — group by theme:
# List projects for the repo owner
gh project list --owner <OWNER>
# Get project number
gh project view <NUMBER> --owner <OWNER>
gh project item-create <PROJECT_NUMBER> --owner <OWNER> \
--title "<Date> — <One-line summary>" \
--body "$(cat <<'EOF'
**What happened:**
- <Concrete changes, linked to PRs/issues>
**Why it matters:**
- <Impact — what's now possible, what's unblocked>
**What's next:**
- <Natural follow-ups, if any>
**Open questions:**
- <Unresolved decisions or risks — omit if none>
EOF
)"
One update per PR
Status without context
Missing links