orwa-mahmoud
UserAccountable long-running coding shifts for Cursor, Codex, and Claude Code. Safe autonomy, recovery, persistent state, and reviewable results a clear view of what’s done, in progress, parked, or blocked—without scrolling a marathon chat.
Categories
Indexed Skills (8)
setup
Scaffold .nightshift/ from the templates and propose stack-aware quality gates — ask, never impose. Private by default.
start
Begin the shift — preflight, clear stale markers, set a deadline only when it means something, then work the punch list.
hunt
Write a ready-made overnight job — coverage hunt, defect hunt, or the standing loop — as a work order with its hours; cut into the punch list only when the owner says start.
nightshift
Run an accountable autonomous shift — work a punch list to completion without clocking out early, park decisions instead of asking, and leave receipts. Use when the user wants to work through a todo list autonomously, run overnight, "don't stop until it's done", "keep going until the list is clear", add test coverage overnight, find and fix everything, or keep reviewing until it's clean.
archive
File the finished part of the run state into a dated archive — shipped items, the rotated journal, handled snags. The live files stay lean; the facts stay on disk.
quality
Survey the project's existing quality debt — lint, types, dead code — and propose punch-list items. Read-only scan; proposes, never imposes.
status
Read-only shift status — open vs ticked items, parked decisions, snag-log summary, deadline remaining, and any STOP/stall state. Starts no work.
stop
Issue a stop-work order — end the shift at once, leaving open items honestly open.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.