All authors
Claude Skills by GeiserX
github.com/GeiserX76 skills0 installs5 views
- Docs LoopAudits repository documentation against current default-branch evidence, reports stale claims, and optionally applies isolated documentation-only fixes or opens reviewable pull requests. Use only when explicitly invoked as /docs-loop.Votes: 0GitHub stars: 4
- ImplementImplements a requested change with the smallest complete diff, splitting genuinely independent work across parallel agents with non-overlapping file ownership, then integrates and verifies it. Use when invoked explicitly to build a feature or change.Votes: 0GitHub stars: 4
- InvestigateInvestigates a bug or unexpected behavior from reproduction to root cause with a panel of independent hypothesis agents, then fixes it only when the request asks for a fix. Use when invoked explicitly to debug, diagnose, or fix a reported failure.Votes: 0GitHub stars: 4
- Refine LoopRuns a safe, resumable refinement loop over a working repository. It discovers behavior-preserving improvements through four evidence-based lenses, ranks them by ROI, applies one small change at a time, verifies independently, and stops deterministically at diminishing returns or a safety limit. Use when explicitly asked to run refine-loop on an existing project.Votes: 0GitHub stars: 4
- ResearchResearches a question with independent parallel specialists that gather evidence from the code, its history, and primary sources, then synthesizes a ranked, cited answer. Use when invoked explicitly for research before a decision.Votes: 0GitHub stars: 4
- Review CodeAudits a whole codebase in bounded waves of independent parallel auditors, publishes every verified finding ranked by severity, and applies only safe, in-scope repairs. Use when invoked explicitly for a codebase health review.Votes: 0GitHub stars: 4
- Review PrReviews a pull request with independent parallel reviewers, verifies every finding, fixes the valid in-scope ones, and has an independent reviewer re-check the result. Use when invoked explicitly on a PR.Votes: 0GitHub stars: 4
- Sergio LoopRuns a durable inspect/plan, implement, verify, and fresh-review loop toward an explicit repository goal, with optional lease-backed coordination across sessions. Use only when the user explicitly invokes sergio-loop.Votes: 0GitHub stars: 4
- ImplementImplements a requested change with the smallest complete diff, splitting genuinely independent work across parallel agents with non-overlapping file ownership, then integrates and verifies it. Use when invoked explicitly to build a feature or change.Votes: 0GitHub stars: 4
- InvestigateInvestigates a bug or unexpected behavior from reproduction to root cause with a panel of independent hypothesis agents, then fixes it only when the request asks for a fix. Use when invoked explicitly to debug, diagnose, or fix a reported failure.Votes: 0GitHub stars: 4
- ResearchResearches a question with independent parallel specialists that gather evidence from the code, its history, and primary sources, then synthesizes a ranked, cited answer. Use when invoked explicitly for research before a decision.Votes: 0GitHub stars: 4
- Review CodeAudits a whole codebase in bounded waves of independent parallel auditors, publishes every verified finding ranked by severity, and applies only safe, in-scope repairs. Use when invoked explicitly for a codebase health review.Votes: 0GitHub stars: 4
- Review PrReviews a pull request with independent parallel reviewers, verifies every finding, fixes the valid in-scope ones, and has an independent reviewer re-check the result. Use when invoked explicitly on a PR.Votes: 0GitHub stars: 4
- Kb ResearchAnswers a question from the team's own record (chat archives, call transcripts, tickets, wiki pages, notes, any mix) through a knowledge-base adapter you fill in. Read-only, never from memory, every claim cited to the source it came from. Use when invoked explicitly to find what the team said or decided, who owns something, or whether a plan contradicts an earlier decision.Votes: 0GitHub stars: 4
- Kb ReviewReviews a pull request the way the team's reviewers do, grounded in reviewer learnings and past decisions captured in your knowledge base, verifies every finding against the code, and reports a severity-ranked review. Reports only; never posts, approves or merges without explicit instruction. Use when invoked explicitly on a PR, your own before requesting review or a teammate's.Votes: 0GitHub stars: 4
- Kb ResearchAnswers a question from the team's own record (chat archives, call transcripts, tickets, wiki pages, notes, any mix) through a knowledge-base adapter you fill in. Read-only, never from memory, every claim cited to the source it came from. Use when invoked explicitly to find what the team said or decided, who owns something, or whether a plan contradicts an earlier decision.Votes: 0GitHub stars: 4
- Kb ReviewReviews a pull request the way the team's reviewers do, grounded in reviewer learnings and past decisions captured in your knowledge base, verifies every finding against the code, and reports a severity-ranked review. Reports only; never posts, approves or merges without explicit instruction. Use when invoked explicitly on a PR, your own before requesting review or a teammate's.Votes: 0GitHub stars: 4
- Docs LoopAudits repository documentation against current default-branch evidence, reports stale claims, and optionally applies isolated documentation-only fixes or opens reviewable pull requests. Use only when explicitly invoked as /docs-loop.Votes: 0GitHub stars: 4
- Refine LoopRuns a safe, resumable refinement loop over a working repository. It discovers behavior-preserving improvements through four evidence-based lenses, ranks them by ROI, applies one small change at a time, verifies independently, and stops deterministically at diminishing returns or a safety limit. Use when explicitly asked to run refine-loop on an existing project.Votes: 0GitHub stars: 4
- Sergio LoopRuns a durable inspect/plan, implement, verify, and fresh-review loop toward an explicit repository goal, with optional lease-backed coordination across sessions. Use only when the user explicitly invokes sergio-loop.Votes: 0GitHub stars: 4
- ArchitectSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.Votes: 0GitHub stars: 4
- ArenaSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.Votes: 0GitHub stars: 4
- Automate MeUse for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences or working style into a skill\", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.Votes: 0GitHub stars: 4
- BabysitWatch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.Votes: 0GitHub stars: 4
- Blast RadiusFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.Votes: 0GitHub stars: 4
- Create Verification SkillGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.Votes: 0GitHub stars: 4
- Figure It OutDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.Votes: 0GitHub stars: 4
- HowUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.Votes: 0GitHub stars: 4
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 4
- No CommentsSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.Votes: 0GitHub stars: 4
- Poteto Modepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.Votes: 0GitHub stars: 4
- Principle Boundary DisciplineApply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.Votes: 0GitHub stars: 4
- Principle Build The LeverApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.Votes: 0GitHub stars: 4
- Principle Encode Lessons In StructureApply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.Votes: 0GitHub stars: 4
- Principle Exhaust The Design SpaceApply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.Votes: 0GitHub stars: 4
- Principle Experience FirstApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.Votes: 0GitHub stars: 4
- Principle Fix Root CausesApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.Votes: 0GitHub stars: 4
- Principle Foundational ThinkingApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.Votes: 0GitHub stars: 4
- Principle Guard The Context WindowApply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.Votes: 0GitHub stars: 4
- Principle Laziness ProtocolApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.Votes: 0GitHub stars: 4
- Principle Migrate Callers Then Delete Legacy ApisApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.Votes: 0GitHub stars: 4
- Principle Minimize Reader LoadApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.Votes: 0GitHub stars: 4
- Principle Model The DomainApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.Votes: 0GitHub stars: 4
- Principle Never Block On The HumanApply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.Votes: 0GitHub stars: 4
- Principle Outcome Oriented ExecutionApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.Votes: 0GitHub stars: 4
- Principle Prove It WorksApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'Votes: 0GitHub stars: 4
- Principle Redesign From First PrinciplesApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.Votes: 0GitHub stars: 4
- Principle Separate Before Serializing Shared StateApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.Votes: 0GitHub stars: 4
- Principle Sequence Verifiable UnitsApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.Votes: 0GitHub stars: 4
- Principle Subtract Before You AddApply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.Votes: 0GitHub stars: 4