All authors
Claude Skills by blackorange0506
github.com/blackorange050611 skills0 installs1 views
- AppNavigationOpen the app at the screen a ticket describes — from a ticket key, a ticket URL, free spec text, or a todo item whose text is `/appNavigation` with the spec as sub-bullets. App-specific: this skill is a placeholder until you implement it for your app; until then it says so and stops. Use when the user wants the app opened where a ticket points — phrases like '/appNavigation PROJ-321', 'open the app at this screen', 'reproduce PROJ-321 on my device'.Votes: 0GitHub stars: 4
- TodoArchiveMove every done ([x]) item out of the user's todo file (TODO.<git user.name>.md, resolved as in the todo rules) into TODO.<git user.name>.archive.md, verbatim, and report what moved. Done items are never deleted — the archive keeps the ids so the next id stays unique, and git picks the move up in the user's normal commits (no git checks, no commits by this skill). Use when the user wants to clean the done prompts out of the todo file — phrases like '/todoArchive', 'archive the done items', 'r...Votes: 0GitHub stars: 4
- TodoFromTicketTurn one ticket into draft prompt items in the user's todo file (TODO.<git user.name>.md, resolved as in the todo rules): fetch the ticket from the configured tracker (Jira via the Atlassian MCP server, GitHub Issues via gh, or the ticket text pasted after the key), download its attachments to <attachmentsDir>/<KEY>/, then append a `## KEY — summary` ticket block with 1–5 numbered dev items, each carrying the ticket key right after its id (`- [ ] #32 PROJ-123 prompt`), then 1–5 `QA:` items (`...Votes: 0GitHub stars: 4
- TodoHelpPrint the Prompt TODO cheat sheet, most important first: what to type to work an item (#12, #new, #newCam, #new1, a pasted line), how to finish one (works, fixed, works #12) and what that does, then the skills table from the flow readme (/todoFromTicket, /todoIdealPrompt, /todoReverse, /todoArchive …). Read-only; touches nothing. Use when the user asks how the todo flow works or what to type — phrases like '/todoHelp', 'todo help', 'how do I use the todo', 'what do I type to work an item', 'h...Votes: 0GitHub stars: 4
- TodoIdealAllSweep the user's todo file (TODO.<git user.name>.md, resolved as in the todo rules) at the end of a session: replace the text of every done ([x]) item that was worked in THIS conversation with its distilled ideal prompt (same distillation rules as /todoIdealPrompt). Done items with no dialog in this session are left untouched and listed as skipped — no honest ideal prompt can be distilled without their dialog. Ids are never assigned, renumbered, or reused. Use when the user wants to batch-upd...Votes: 0GitHub stars: 4
- TodoIdealPromptDistill a finished TODO-item dialog into the IDEAL PROMPT — the single SHORT message (a few typeable lines, never a spec) that would have produced the confirmed result on the first try — plus feedback on what the original prompt lacked. Prompt-writing training for the user: Claude reconstructs the whole back-and-forth (original prompt, every correction, the final accepted fix) and writes the prompt it wishes it had received. With --replace, the item's text in the user's todo file (TODO.<git u...Votes: 0GitHub stars: 4
- TodoMarkCodeTurn the code markers of Prompt TODO on or off — the `[<name>#N]` tag Claude appends to a comment at each change site so grep leads from code back to the todo item. Writes `codeMarkers` in .claude/prompt-todo/config.json and re-renders .claude/prompt-todo/RULES.md; touches no code and no todo file. Existing markers stay either way. Runs only when the user invokes it: '/todoMarkCode', '/todoMarkCode on', '/todoMarkCode off'.Votes: 0GitHub stars: 4
- TodoNumberAssign ids on demand to the placeholder items in the user's todo file (TODO.<git user.name>.md, resolved as in the todo rules): every top-level `- [ ] #new …`, `- [ ] #newX …` or id-less `- [ ]` line gets the next id (highest #N present in the file and its archive, plus one), sloppy `- []` is normalised, and the token→id mapping is reported. Starts no work — it is the explicit form of the Autoincrement rule that otherwise runs on any touch. Use when the user just wants numbers — phrases like ...Votes: 0GitHub stars: 4
- TodoReverseThe reverse of the normal flow: turn a piece of work that was done straight through the terminal WITHOUT a todo item — a hotfix, a quick 'fix this' with its corrections — into an item in the user's todo file (TODO.<git user.name>.md, resolved as in the todo rules) after the fact. Distills that dialog into its ideal prompt (same rules as /todoIdealPrompt), appends it with the next id as a done `- [x] #N` item (or open with --open), and adds the `[<name>#N]` markers at the change sites of that ...Votes: 0GitHub stars: 4
- TodoScoreTurn the prompt scores of Prompt TODO on or off — the ` (N/5)` Claude appends to an item line when it rewrites the item to its ideal prompt, rating how close the original prompt was. Writes `promptScores` in .claude/prompt-todo/config.json and re-renders .claude/prompt-todo/RULES.md; touches no todo file. Existing scores stay either way. Runs only when the user invokes it: '/todoScore', '/todoScore on', '/todoScore off'.Votes: 0GitHub stars: 4
- TodoSetupThe configuration wizard for Prompt TODO: seven steps (todo file + title, tags, rules check, ticket tracker, app navigation, permissions, summary), each one skippable and re-runnable on its own, --yes takes every default. Edits .claude/prompt-todo/config.json and re-renders .claude/prompt-todo/RULES.md. Runs only when the user invokes it: '/todoSetup', '/todoSetup tags', '/todoSetup tracker', '/todoSetup --yes'.Votes: 0GitHub stars: 4