techdufus
- 17 skills
- 0 followers
- 9 hours ago last updated
- ▌ Commit 2 · techdufus bundleCreate a conventional commit from current workspace changes. Use when the user asks to run $commit, asks to commit changes, or asks for a commit message from the current diff.
- ▌ Init Deep · techdufusInitialize or migrate to nested CLAUDE.md structure for progressive disclosure. Claude auto-loads CLAUDE.md from any directory it reads, enabling true contextual guidance. Triggers on: '/init-deep', 'deep init', 'initialize deeply', 'setup claude deeply', 'refactor claude.md', 'migrate claude.md', 'nested claude', 'progressive disclosure'.
- ▌ Ralph Plan · techdufusStructured PRD generation with interview, research, and approval workflow. Triggers on: '/ralph-plan <topic>', 'create prd', 'generate prd', 'plan this'. Creates comprehensive Product Requirements Document via interview and research.
- ▌ Ralph Loop Init · techdufusTransform approved plans into ralph loop infrastructure. Triggers on: '/ralph-loop-init', '/ralph-init', 'setup ralph loop', 'generate ralph loop'. Creates .ralph/ directory with prd.json, loop.py, CLAUDE.md, and supporting files.
- ▌ Git Commit Validator · techdufusMUST be used for ANY git workflow that involves committing code. This includes explicit commit requests AND implicit ones like 'ship it', 'wrap it up', or finishing implementation work. Handles staging, message generation, validation, and commit execution with conventional commit format.
- ▌ Oh My Claude Runtime · techdufusUse when applying oh-my-claude workflow guidance, ultrawork modes, agent orchestration, plan execution, or plugin configuration.
- ▌ Orca · techdufusOptional magic words to put in an Orca worker spec for Cursor or OMP. Use only when the user invokes /orca or /skill:orca, while following the orchestration skill. Not the Orca CLI and not how to structure the spec.
- ▌ Work · techdufus bundleUse when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
- ▌ Commit · techdufusPreparing and creating local commits at meaningful verified checkpoints or on explicit request; covers staged diff review, secrets checks, and conventional commit messages.
- ▌ Intent · techdufusExtract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.
- ▌ Verification · techdufusVerifying effective state and idempotence for Ansible role, playbook, and repository-managed configuration changes.
- ▌ Omp Release Config Audit · techdufus bundleAudit recent OMP releases against project configuration, effective runtime behavior, optional features, extensions, and maintenance drift using source-backed evidence.
- ▌ Ultrathink · techdufusFirst-principles reasoning for this turn: separate verified facts from inherited assumptions, rebuild the approach, then act. Use when the user invokes /ultrathink or the requested solution may be the wrong shape. Not an effort-level override and not a substitute for /orchestrate.
- ▌ Orchestrate · techdufusMaximum-effort multi-agent orchestration: enumerate the full surface, fan out parallel Task subagents, verify each phase, and continue until done. Use only when the user invokes /orchestrate. Not the default delegation path.
- ▌ Herdr Workflow · techdufus bundleRoute durable OMP handoffs through Herdr: topology, prompt trust, ownership, cleanup. Use only for explicit requests, including /skill:herdr-workflow; not ordinary coding, in-process delegation, worktree questions, or general Herdr CLI help.
- ▌ Ultraresearch · techdufusExhausts sources with parallel WebSearch, WebFetch, and explore, then cross-checks and cites. Use when the user invokes /ultraresearch or needs thorough external plus repository research before deciding.
- ▌ Github Issue Hierarchy · techdufus bundleCreate GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.