All authors
Claude Skills by dryvist
github.com/dryvist66 skills0 installs124 views
- AlphaFirst fixture skillVotes: 0GitHub stars: 3
- BetaSecond fixture skillVotes: 0GitHub stars: 3
- GoalEmit one goal statement for current work, capped under 4000 chars. Optional focus hint like /compact. Derives from recent pivots/plan/tasks if no arg. Use for 'what am I trying to do' or seeding a session/subagent.Votes: 0GitHub stars: 3
- ReplanRebuild a plan from live ground truth (artifacts, tests, git/gh) when it no longer matches reality — items done, approach superseded, facts drifted. Use when a plan goes stale or resuming reveals contradictions. Never trusts the plan's own prose.Votes: 0GitHub stars: 3
- ResumePick up unfinished work cold by re-deriving state from live git, gh, the plan file, and TaskList — never from remembered claims. Use at the start of a session continuing prior work. Verifies what's merged, open, committed, checked-off first.Votes: 0GitHub stars: 3
- Session StatusAnalyzes current session state, no cleanup. Full mode (default): plan+TaskList+history scan, emits a next-session prompt. Mid mode (`/session-status mid`): fast 'done vs remaining' snapshot. Repo/PR state is optional; both modes run outside a repo.Votes: 0GitHub stars: 3
- Track FollowupsRecord triaged follow-up work where it'll be seen: create the item in Vikunja or Zammad (incidents), deduplicating first and reporting the id. Use when session work outlives it or items were triaged elsewhere. Never opens a GitHub issue.Votes: 0GitHub stars: 3
- Wrap Up DocsEmit a paste-ready prompt for a weaker LLM to update public/private docs from this session's changes: per-item changelog, fixed routing, docs-only scope fence. Read-only, git-first evidence. Use at session end before delegating docs.Votes: 0GitHub stars: 3
- Wrap UpEnd-of-session handler: checks if the plan is complete. If complete: quick retrospective, forward follow-up prompt, and (in a repo) refresh + clean gone branches. If incomplete: skip cleanup, emit resume prompts. Cleanup needs a repo; rest doesn't.Votes: 0GitHub stars: 3
- Auto MaintainAutonomous maintenance orchestrator that continuously finds and dispatches workVotes: 0GitHub stars: 3
- Delegate To AiRoute non-sensitive coding and review to ZCode jobs or live sessions by default; select native agents, Codex, or local models for other work.Votes: 0GitHub stars: 3
- Fast SubagentUse for any routine/checkable step — summarize, extract, classify, reformat, draft boilerplate, first pass over a file — every such step, all session. Sends to the router's fast-subagent role, which picks backend/fallback. Names no model ids.Votes: 0GitHub stars: 3
- Local SubagentsUse for bulk reading, summarizing, classifying, extracting, drafting boilerplate, or a first pass over code — hand it to a local/cheap model via the router, not your context. Covers delegation timing, the model menu, bounding calls, refusals.Votes: 0GitHub stars: 3
- Multi Model ReviewFan a plan/diff to independent model families — cloud coding-agent CLI, cloud reasoning-agent CLI, local model server — for adversarial review, plus each invocation's gotcha. Use for a second opinion, a suspect verdict, or an offline reviewer.Votes: 0GitHub stars: 3
- Openrouter ModelsChoose among the router's hosted models — discover current ids/prices from the public catalog, self-enforce a spend budget the router doesn't meter, respect the free-tier logging caveat, and request onboarding of a model not yet served.Votes: 0GitHub stars: 3
- Premium Agent OrchestrationUse when the session runs a premium top-tier/SOTA model AND the work is independent pieces exceeding one context window, or insurance against an occasional runaway task in a large routine batch. Fans work to cheaper agents or local/free LLMs while the lead keeps judgment, merging, and verification. Not for serial work with a few decisions or a single chain fitting one context — tune effort on one model instead.Votes: 0GitHub stars: 3
- Code Quality StandardsUse when writing or reviewing code, choosing a logging format, or deciding between continuous monitoring and one-time tests in this estateVotes: 0GitHub stars: 3
- Codeql Permission ClassificationPermission requirements for GitHub ActionsVotes: 0GitHub stars: 3
- Github Workflow Security PatternsCanonical security patterns for GitHub Actions workflowsVotes: 0GitHub stars: 3
- Validate ReadmeValidate all README files in the repository for required sections and installation code blocks, and score each one 0-6 on a quality rubric (purpose paragraph, quickstart, usage examples, license, length). Checks section presence using config from .readme-validator.yaml or sensible defaults. Badge URL reachability is checked on-demand via WebFetch.Votes: 0GitHub stars: 3
- Git Workflow StandardsUse when managing branches, resolving merge conflicts, syncing with the default branch, or working with worktrees. Covers both trunk repos (main) and git-flow repos (develop) — see gh-cli-patterns (github-workflows) for default-branch detection.Votes: 0GitHub stars: 3
- Pr StandardsUse when creating PRs, linking issues, managing PR comments, or creating GitHub issuesVotes: 0GitHub stars: 3
- Git Flow NextWork with repositories using the git-flow-next branching model (default branch is `develop`, production branch is `main`). Covers branch creation, worktree setup, atomic commits, PR targeting, validation on `develop`, and mandatory end-of-session promotion to `main`.Votes: 0GitHub stars: 3
- Pre Commit ArchitectureUse when adding/editing .pre-commit-config.yaml, wiring pre-commit hooks into a repo, or scaffolding a new repo's lint/hook setup. Covers the canonical nix-devenv/dryvist-.github architecture, profiles, and consumer patterns.Votes: 0GitHub stars: 3
- Sync MainUpdate the repo's default branch from remote and merge it into the current branch, or all open PR branches. Despite the name (kept for continuity), this syncs whatever the repo's default branch actually is — main on trunk repos, develop on git-flow repos — and on git-flow repos also fast-forwards local main from origin/main.Votes: 0GitHub stars: 3
- Troubleshoot PrecommitTroubleshoot pre-commit hook failures and auto-fixesVotes: 0GitHub stars: 3
- Troubleshoot RebaseDiagnose and recover from git rebase failuresVotes: 0GitHub stars: 3
- Troubleshoot WorktreeTroubleshoot git worktree, branch, and refname issuesVotes: 0GitHub stars: 3
- Finalize PrAutomatically finalize pull requests for merge by resolving CodeQL violations, review threads, merge conflicts, and CI failures. Handles single PR (current branch or by number), all open PRs in the repo, or all open PRs across the org. Includes bot-authored PRs in all modes.Votes: 0GitHub stars: 3
- Gh Cli PatternsCanonical reference for all gh CLI command shapes used by skills in this plugin. Defines the placeholder convention, default-branch (trunk vs git-flow) detection, allowed --json fields, GraphQL fallback rules, -f/-F/--raw-field flag semantics, the PR-readiness gate, code-scanning alert query, review-thread fetch/count/resolve mutations, and heredoc bodies. Prevents Unknown JSON field errors and divergent query shapes.Votes: 0GitHub stars: 3
- Github Actions Silent FailuresDiagnose GitHub Actions workflows that fail silently — a reusable-workflow run with zero jobs/logs, a gh-aw import mis-resolving vs a repo named .github, self-hosted-runner traps. Use when a required check never reds or a run has no jobs.Votes: 0GitHub stars: 3
- Github Code SearchSearch real code across ~1M public GitHub repos via grep.app — use to see how others solved something, find real API/config-key usage, check if a pattern is idiomatic, or gather prior art. Works via the grep MCP server or a keyless HTTP fallback.Votes: 0GitHub stars: 3
- Issue SweepUse when a tracker's open issues piled up, went stale, or stopped reflecting reality — maybe fixed, duplicated, vague, superseded — reconcile against actual code, group by root cause, turn into a plan. Any tracker. Use before a work session too.Votes: 0GitHub stars: 3
- Merge PrMerge a PR into its base branch. Defaults to a merge commit; pass --squash or -s to squash instead. Falls back to squash when the repo disallows merge commits. Single PR by number or current branch. Refuses to squash/rebase into main on a git-flow repo — use /promote-release there instead.Votes: 0GitHub stars: 3
- Pr StacksUse when a change is too large for one PR, when the next unit of work depends on an unmerged PR, or when GitHub stacked pull requests / `gh stack` come up. The single source of truth for the PR-stack concept and the local pre-GitHub workflow: layering branches, keeping layers rebased, and landing a stack without fighting branch protection.Votes: 0GitHub stars: 3
- Pr SweepUse when open PRs piled up in one repo or an owner's repos and you want them triaged and driven to zero in one pass — bot/teammate-authored included. Also for sweeps running many repos in parallel without racing approvals or flooding CI.Votes: 0GitHub stars: 3
- Promote ReleaseOpen and merge a develop-to-main promotion PR on a git-flow repo. Merge commit only, never squash or rebase — main accepts merge commits only. Every merge to main triggers release-please, which takes over tagging and release notes from there. Refuses on trunk repos (default branch main) — use /merge-pr instead.Votes: 0GitHub stars: 3
- Prune BranchesDelete branches and worktrees with nothing useful — zero commits ahead of default, or a matched merged PR — local and remote, single-repo or workspace-wide. Run after refresh-repo syncs the default branch.Votes: 0GitHub stars: 3
- Rebase PrLocal rebase-merge workflow for pull requests with signed commits, pushed directly to the PR's base branch. Refuses on git-flow repos when the base is main — direct pushes to main are banned there; use /promote-release.Votes: 0GitHub stars: 3
- Refresh RepoCheck PR merge readiness and sync the local repo with its default branch. See prune-branches (github-workflows) for stale branch and worktree cleanup.Votes: 0GitHub stars: 3
- Resolve Pr ThreadsOrchestrates resolution of GitHub PR review threads AND reads recent non-thread PR comments (top-level + review bodies) by grouping related feedback, processing each group sequentially inline with superpowers:receiving-code-review, and resolving threads via GraphQL. Use when you need to batch-process review feedback to unblock a PR merge.Votes: 0GitHub stars: 3
- Shape IssuesShape raw ideas into actionable GitHub Issues using Shape Up methodologyVotes: 0GitHub stars: 3
- Shared Workflow Org RefsUse when creating or editing GitHub Actions workflows that call reusable workflows (uses: OWNER/repo/.github/workflows/...) — org owner references must be the literal current org, and shared-CI homes are under dryvist.Votes: 0GitHub stars: 3
- ShipCommit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.Votes: 0GitHub stars: 3
- Trigger Ai ReviewsUse when asked to "trigger AI reviews", "request AI re-reviews", "get Claude/Gemini/Copilot to review my PR", "re-review this PR", or trigger review-request comments on a PR. Triggers all three AI reviewers by default, or specific ones when named.Votes: 0GitHub stars: 3
- Dell Idrac Bmc OpsBring a Dell PowerEdge BMC (iDRAC) onto the network headlessly, standardize settings, stage firmware, drive an unattended install — Redfish/racadm gotchas, identity-before-power, phantom-drive from stale firmware. Use bringing up/diagnosing a BMC.Votes: 0GitHub stars: 3
- Homelab RunbooksUse when powering on a sleeping DR node, converging DNS records for a new ingress vhost, or bringing up OpenBao/Terrakube JWT identity — homelab operational runbooks for power management, DNS, and secrets-engine bring-up.Votes: 0GitHub stars: 3
- Llm Router OpsOperate a self-hosted OpenAI-compatible LLM router — client-wiring per client, context-window ad gotcha, env-vs-persisted-config gotcha, why an unauth health probe should 401. Use wiring a client, adding a backend, diagnosing misbehavior.Votes: 0GitHub stars: 3
- Proxmox Cluster OpsOperate a Proxmox VE cluster safely — read-only inspection with pvesh/pct/qm/pvecm instead of hand-editing a live guest, quorum-respecting node updates, joining a new node. Use for cluster/guest inspection, rolling updates, or adding a node.Votes: 0GitHub stars: 3
- Pxe NetbootReliable remote OS install over PXE when virtual-media/KVM is broken — proxyDHCP+TFTP via dnsmasq, kernel/initrd over HTTP, custom iPXE with embedded autoexec. Use when a BMC's virtual CD is unreliable or a headless install needs netboot.Votes: 0GitHub stars: 3