All authors
Claude Skills by doodledood
github.com/doodledood37 skills4 installs148 views
- Harden Task FileHarden /define task guidance files for one-shot quality. Iterates: orthogonality gap analysis, user-approved additions, prompt review, fix, converge. Use when a task file needs comprehensive coverage or "harden task file".Votes: 0GitHub stars: 73
- Learn From SessionAnalyze Claude Code sessions to learn what went right/wrong and suggest high-confidence improvements to skills. Use when asked to analyze a session, learn from a session, or review workflow effectiveness.Votes: 0GitHub stars: 73
- Review PromptReview LLM prompts against the prompt-engineering skill''s principles — leading with where each line came from — and report the findings without modifying files. Use when reviewing prompt quality, auditing a prompt, evaluating a system prompt, or checking whether prompt issues are high-confidence and fixable.Votes: 0GitHub stars: 73
- Sync Claude Code PluginsSync the prompt-engineering plugin from a local clone of claude-code-plugins into .claude/ so the repo is self-contained for isolated/web environments. Copies agents/skills, removes only previously-synced items that disappeared upstream. Other content in .claude/ is left alone. Use when asked to sync claude-code-plugins, pull prompt-engineering, refresh prompt-engineering plugin.Votes: 0GitHub stars: 73
- Sync ToolsRegenerate the Codex distribution copy of the plugin skills and check it for drift. Run after changing anything under claude-plugins/*/skills. OpenCode and Pi read the source tree directly and need no sync.Votes: 0GitHub stars: 73
- ExampleAnalyzes the current project structure and tech stack. Use when asked to explore, understand, or summarize a project. Trigger terms: project overview, analyze codebase, what is this project.Votes: 0GitHub stars: 73
- AdrAccepted — narrowed by 20260830-a-contract-slot-exists-only-where-its-value-is-known: the chain prefix's path-recording clause moves into the goal block and the `<manifest-path>` slot is removed; the beat-naming rule this record set stands. Further narrowed by 20260905-executors-own-path-bearing-continuation-goals: auto chains defer continuation to execution; executors include the known Manifest path and the shared chain prefix is retired.Votes: 0GitHub stars: 73
- HandoffProduce a self-contained context payload that lets a fresh agent continue without re-deriving what this session established. Use for cross-boundary transfer such as switching tools, starting a clean session, or handing off to another agent, and for DIY delegation flows where a focused side-session returns context to the parent.Votes: 0GitHub stars: 73
- Prompt EngineeringCreate, update, review, or discuss an LLM prompt — a system prompt, a skill, or an agent. Use when writing or improving a prompt, discussing a skill or agent, diagnosing prompt failures, or when the user says a prompt needs work.Votes: 0GitHub stars: 73
- Review PrAutonomous PR review that posts high-signal, human-voiced comments under your account. Use when reviewing someone else''s PR or your own manifest-driven PR, when you want a precision-tuned review you can walk away from, or when the user asks to review a PR, post a PR review, autoreview, loop review, or watch a PR.Votes: 0GitHub stars: 73
- Walk PrWalk through a PR or large diff together — your own or someone else''s — one sub-changeset at a time and one review topic at a time within it. Use when reviewing a substantive PR collaboratively, walking a large refactor, or when the user asks to walk a PR, walk a diff, explain a PR, review collaboratively, or review a change together. Optional --canvas runs the walk in a live HTML artifact.Votes: 0GitHub stars: 73
- AutoEnd-to-end autonomous execution: figure-out → define → do, chained without manual approval gates. Use when you want to define and execute without intervention during planning, when the user asks for autonomous or end-to-end work, or asks to go from idea to done without approval gates.Votes: 0GitHub stars: 73
- DefineManifest builder. Turns shared understanding into a verifiable Manifest with Deliverables, Acceptance Criteria, Global Invariants, and an Initial Approach. Use when planning features, scoping refactors, debugging complex issues, or when the user asks to define, scope, plan, spec out, make a manifest, or break down a task.Votes: 0GitHub stars: 73
- DoManifest executor. Reads a Manifest and pursues it with full autonomy: reach a state where every Acceptance Criterion and Global Invariant holds, deciding for itself how to get there. Use when executing a manifest, running a plan, implementing a defined task, or when the user asks to run, execute, implement, or ship a manifest-backed plan.Votes: 0GitHub stars: 73
- DoneCompletion marker for the /do workflow. Outputs a plain-prose summary of what was built. Called by /do after every Acceptance Criterion and Global Invariant has fresh PASS evidence, when the manifest is complete, all criteria pass, or the workflow needs to wrap up with a completion summary.Votes: 0GitHub stars: 73
- EscalateTerminal escalation for do when unresolved blockers require outside intervention and no useful independent work remains. Reports the evidence, recovery attempts, completed work, and intervention needed.Votes: 0GitHub stars: 73
- Figure Out TeamDrive a multi-party deliberation in a Slack channel or thread. The agent is an involved orchestrator — presses rigorously, brings evidence, names trade-offs, surfaces disagreements, advances when answers cohere; owner-by-Slack-handle overrules. Use when the people involved cannot all sit in one chat, when deliberation has to happen in Slack, or when the user asks to figure out with the team, press a group asynchronously, or get the team aligned.Votes: 0GitHub stars: 73
- Figure OutFigure things out together — any topic, problem, or idea. Presses relentlessly until shared understanding is reached. Use when understanding is the deliverable rather than a preamble to acting, when figuring it out is the goal, or when the user asks to think through a decision, dig deeper, press an assumption, investigate why something is happening, or work through a problem.Votes: 0GitHub stars: 73
- Babysit PrAuthor-side PR lifecycle babysitter and companion to review-pr. Use when the user wants to tend an existing GitHub PR through CI, review threads, description sync, mergeability, auto-fixes, or asks to babysit a PR with or without an existing manifest.Votes: 0GitHub stars: 73
- Eli5Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.Votes: 0GitHub stars: 73
- Teach MeTeach the learner to deeply understand a body of work — the current session's changes, a PR, an ADR, or any topic they name — the problem and why it existed, the solution and why it was built that way, and why it matters, incrementally and confirming mastery at each stage before advancing. Use when the user wants to understand what was just built or changed, asks to be taught or walked through a change, or wants to learn the why behind the work — e.g. "teach me what we did", "teach me this PR...Votes: 0GitHub stars: 73
- Check PrRead-only inspection of a single GitHub PR lifecycle — checks CI, review threads, description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress, checking mergeability, or babysitting a GitHub PR through CI and approvals.Votes: 0GitHub stars: 73
- DesignGuide visual and interaction design from the person, moment, and subject, with composable guidance for artifacts and creative directions. Use when creating or restyling a page, app, document, presentation, graphic, or prototype, or choosing how it should look and feel.Votes: 0GitHub stars: 73
- Init ContextSet a project up with the surfaces manifest-dev works from — a North Star, a glossary, ADR conventions, and the context-file wiring that makes every session use them — seeding them from the project''s own history where there is any. Use when a repository has no CONTEXT.md or decision records, when adopting manifest-dev in an existing codebase, when starting a new project, or when the user asks to initialize project context, bootstrap ADRs, or reconstruct decisions from history.Votes: 0GitHub stars: 73
- Next TicketRead the project''s Ticket store, choose the single best Ticket for the human-plus-AI session to work on now, claim it, and present it with the reason it leads. Use when asking what''s next, what should I work on, or pulling the next Ticket from the backlog. Selection stops after presentation; execution belongs to run-ticket or the person holding the claim.Votes: 0GitHub stars: 73
- Poll SlackNarrate new Slack messages in a channel or thread since a cursor. Returns a natural-language story of what was said, or a clear statement when there is nothing new. Use when a parent agent polls Slack and needs to know what changed, read a Slack delta, or understand a thread update without re-ingesting the whole thread.Votes: 0GitHub stars: 73
- Review CodeReview a change along one specific quality dimension — bugs, design, simplicity, maintainability, testability, test quality, type safety, contracts, operational readiness, docs, prose value, change intent, defect-class completeness after a fix, or context-file adherence. Loads exactly one dimension reference and audits the diff against it, returning a structured PASS/FAIL report with severities. Use when verifying a change before merge, auditing a diff for a named concern, or running a manife...Votes: 0GitHub stars: 73
- Review DesignReview digital artifacts against the user’s task, creative direction, functional and accessibility requirements, and actual delivery medium. Inspect renders, native files, playback or interaction as appropriate; exercise relevant failure and recovery paths and report evidence-backed findings. Use for design review or a manifest gate. Design guidance belongs to design; implementation and restyling stay with the invoking workflow.Votes: 0GitHub stars: 73
- Review WritingReview any prose against this project''s writing standards — a README, a spec, a design doc, a blog post, marketing copy, or a draft you paste in. Detects whether the text is documentation or human-voiced writing, applies that register''s rules plus the rules holding in both, and reports graded findings with the fix. Use when checking a document''s style, asking whether a draft reads as AI-written, reviewing writing before publishing, or asking for a writing review outside a manifest run.Votes: 0GitHub stars: 73
- Run TicketRun one exact Ticket through recovery, autonomous work, and its required landing, then write DONE or ESCALATED evidence back to that same Ticket. Use when a hosted trigger, agent runner, or person supplies a specific issue, tracker item, or file Ticket to work end to end. This skill does not select backlog work or enforce Auto eligibility at dispatch.Votes: 0GitHub stars: 73
- Sweep TicketsRecover or start one unattended Ticket from a configured shared Ticket Store, then stop. Use from a scheduled agent trigger to resume one interrupted automation-owned Auto Ticket or select one ready Auto Ticket and invoke run-ticket. This is the low-frequency correctness path beside issue-event triggers, not a backlog batch runner.Votes: 0GitHub stars: 73
- Ticket UpAuthor self-sufficient Tickets in the project''s store from a finished Manifest, a direct work request, an open question, or follow-up findings from another Ticket. A Manifest becomes one coherent Shaped Ticket by default; split it by Deliverable only when the caller explicitly wants delegation or parallel pickup. Use when creating Tickets, ticketing up a plan, recording follow-up work, or handing work to a teammate, agent, or later session.Votes: 0GitHub stars: 73
- Prompt EngineeringCreate, update, review, or discuss an LLM prompt — a system prompt, a skill, or an agent. Use when writing or improving a prompt, discussing a skill or agent, diagnosing prompt failures, or when the user says a prompt needs work.Votes: 0GitHub stars: 73
- Review Pr HolisticCalled by review-pr after its reviewer fleet and judgment pass return: consolidates their findings against the PR''s history into the set of comments worth posting — pruning what the PR already covers, merging duplicates, subordinating defects under premise questions, bounding to the reviewed range, and rewriting every body in the caller''s voice. Not for direct use.Votes: 0GitHub stars: 73
- Review Pr JudgmentCalled by review-pr in both of its modes: the whole-PR premise check that asks whether a change earns its keep against the pain it solves, firing only on concrete evidence and returning non-blocking author-facing questions, one per root, with no severity. Not for direct use.Votes: 0GitHub stars: 73
- Review Pr Thread VerifyCalled by review-pr for each unresolved review thread it authored: judges from the thread, the author''s replies, and the current code whether the original concern is addressed, stale, or still standing, and returns exactly one disposition with a drafted reply where one is needed. Not for direct use.Votes: 0GitHub stars: 73
- Manifest To GoalTurn a Manifest into a standalone goal defining what done means, in at most 4,000 characters. Use when the user wants to paste the work into a goal field without a Manifest file reference.Votes: 0GitHub stars: 73