All authors
Claude Skills by gufranco
github.com/gufranco42 skills0 installs46 views
- AsideMid-task side question handler. Freezes the active task state, answers a side question without state mutation, then resumes the task exactly where it stopped. Lighter than /checkpoint save. Use when user says "aside", "quick question", "side question", "while we're at it", "before you continue", or interrupts mid-implementation with an unrelated question. Do NOT use for new scope (use /plan), retro (use /retro), or true context switches (use /checkpoint save).Votes: 0GitHub stars: 2
- AssessmentArchitecture completeness audit for an implementation. Finds missing patterns, planted defects, and opportunities to stand out. Use when user says "assess", "what am I missing", "interview prep", "take-home review", "check my architecture", "pre-submission audit", or wants to verify an implementation covers all engineering patterns before declaring it done. Do NOT use for diff-based code review (use /review), security-only audits (use /audit), or running tests (use /test).Votes: 0GitHub stars: 2
- AuditSecurity audit across dependencies, secrets, Docker, code patterns, images, STRIDE, and OWASP. Absorbs /deps for vulnerability scanning and /cso for threat modeling. Use when user says "security audit", "scan for vulnerabilities", "check dependencies", "find secrets", "audit Docker", "CVE scan", "cso", "threat model", "owasp audit", "deep security scan", or wants to find security issues across the full project. Do NOT use for code review (use /review), architecture completeness (use /assessme...Votes: 0GitHub stars: 2
- BenchmarkPerformance regression detection. Measures API latency, bundle size, and database query time, then compares against saved baselines. Use when user says "benchmark", "performance check", "check for regressions", "bundle size", "latency", "is this slower", or wants to detect performance changes. Do NOT use for code quality scoring (use /health), load testing setup, or profiling.Votes: 0GitHub stars: 2
- BrainRead from and write to the second brain vault. Subcommands - capture (default), ingest, ask, link, health, refresh, falsify, wrong, compile, eval. Files durable knowledge as specced notes, answers questions from what is already stored, keeps the graph honest as facts age, hunts facts that are wrong rather than merely old, and compiles the session memory directory from the vault. Use when user says "capture this", "remember this", "file this", "what do we know about X", "ask the vault", "vault...Votes: 0GitHub stars: 2
- CheckpointSave and resume working state across sessions. Subcommands: save, resume, list. Captures git state, decisions made, remaining work, and modified files so a new session can pick up where the last one left off. Use when user says "checkpoint", "save progress", "save state", "resume", "pick up where I left off", or wants to preserve session context. Do NOT use for git commits (use /ship commit), retrospectives (use /retro), or planning (use /plan).Votes: 0GitHub stars: 2
- CleanupStale branch, PR, and worktree cleanup. Lists branches with no recent commits, PRs open too long, merged branches not deleted, orphaned worktrees, and draft PRs that went stale. Offers to close or delete with confirmation per item. Use when user says "cleanup", "clean branches", "stale PRs", "delete old branches", "prune", "tidy up", or wants to reduce repository clutter. Do NOT use for code cleanup (use /refactor), dependency updates (use /audit deps), or git workflow (use /ship).Votes: 0GitHub stars: 2
- Concise ModeOpt-in terse-reply mode that drops articles, pleasantries, filler, and hedging while keeping full technical accuracy. Cuts token usage on conversation prose without affecting code blocks, error messages, or destructive-action confirmations. Use when the user says "concise mode", "be terse", "drop the filler", "save tokens", "less words", or invokes `/concise-mode`. Disable when the user says "normal mode", "stop concise", or "back to normal".Votes: 0GitHub stars: 2
- Cross ModelConsult a different model for orthogonal reasoning on a consequential decision, especially when confident. Discovers whichever model CLI is installed rather than assuming a vendor. Use when the user says "second opinion", "cross-model", "ask another model", "stress-test this", "what am I missing", "red-team this decision", or before committing to an architecture, a schema, a security boundary, or anything hard to reverse. Do NOT use for reversible local decisions, for questions with one verif...Votes: 0GitHub stars: 2
- DeployMerge PRs, verify deployments, and monitor post-deploy health. Subcommands: land (default), canary. Extends the delivery pipeline past /ship by handling merge, deployment verification, and post-deploy monitoring. Use when user says "deploy", "merge and deploy", "land this PR", "canary", "post-deploy check", "verify deployment", or wants to take a shipped PR through to production. Do NOT use for creating PRs (use /ship pr), running tests (use /test), or CI diagnosis (use /ship checks).Votes: 0GitHub stars: 2
- DesignDesign consultation, variant exploration, and design system scaffolding. Subcommands: consult (default), variants, system. Researches design patterns, proposes component hierarchies, generates design decisions document, and creates multiple visual approaches for comparison. Use when user says "design this", "design consultation", "design system", "component design", "design variants", "UI approach", "visual direction", or needs structured design thinking before implementation. Do NOT use for ...Votes: 0GitHub stars: 2
- ExplainExplain code with educational depth. Generates Mermaid diagrams for architecture and data flow, traces data through the codebase, explains design decisions with rationale, identifies patterns, and suggests improvements. Use when user says "explain", "explain this code", "how does this work", "walk me through", "what does this do", "trace the data flow", or wants to understand a file, directory, or system with educational depth. Do NOT use for code review (use /review), debugging (use /investi...Votes: 0GitHub stars: 2
- Fix IssueFix a GitHub issue by number. Fetches the issue, analyzes requirements, searches the codebase, implements the fix with tests, and commits referencing the issue. Use when user says "fix issue #N", "fix #N", "resolve issue N", "close issue N", or wants to implement a fix for a specific GitHub issue. Do NOT use for general debugging without an issue (use /investigate), code review (use /review), or feature planning (use /plan).Votes: 0GitHub stars: 2
- GanGenerator-Evaluator iteration loop for building features against a scored rubric. Use when user says "gan", "gan loop", "generator evaluator", "iterate to threshold", "build with feedback loop", or needs an iteration pattern stronger than `/loop` for feature work that has a measurable quality signal. Do NOT use for one-shot implementations (use `/plan` + direct edits), recurring schedules (use `/loop`), or visual design exploration (use `/design variants`).Votes: 0GitHub stars: 2
- GuardCombined safety mode for risky operations. Activates directory freeze, destructive command warnings, and scope enforcement simultaneously. Use when user says "guard", "safe mode", "freeze to this directory", "be careful", "restrict edits", or wants extra protection during a risky operation. Do NOT use for debugging (use /investigate), code review (use /review), or general editing.Votes: 0GitHub stars: 2
- HotfixEmergency production fix with expedited workflow. Creates a hotfix branch from the latest release tag, applies the minimal fix, runs critical tests, ships with expedited review, and backports to the main branch. Use when user says "hotfix", "production bug", "emergency fix", "prod is broken", "urgent fix", or needs to fix something in production immediately. Do NOT use for non-urgent bugs (use /investigate), feature work (use /plan), or general debugging (use /investigate).Votes: 0GitHub stars: 2
- IncidentGather incident context and generate a blameless postmortem from the template in observability rules. Use when user says "postmortem", "incident report", "outage report", "what happened", "write a post-mortem", or needs to document an incident with timeline, root cause, and action items.Votes: 0GitHub stars: 2
- InfraManage infrastructure for local development. Subcommands: docker, terraform, db. Covers container orchestration with Colima awareness, IaC workflows with safety gates, and database migrations with ORM detection. Use when user says "docker compose", "start containers", "terraform plan", "run migration", "create migration", "database setup", or needs to manage local dev infrastructure. Do NOT use for deploying to production (use CI/CD), security scanning (use /audit), or Terraform test patterns...Votes: 0GitHub stars: 2
- Interview MeOne-question-at-a-time intent clarification for underspecified or ambiguous asks. Drives toward 95%+ intent confidence before any implementation. Use when user says "interview me", "grill me", "are we sure?", "stress-test my thinking", or when the request is too vague to act on without guessing. Do NOT use for tasks the user has already specified concretely.Votes: 0GitHub stars: 2
- InvestigateSystematic debugging with hypothesis testing, bounded retries, and optional edit freeze. Use when user says "debug this", "investigate", "why is this failing", "find the bug", "trace this error", "root cause", or needs structured debugging beyond reading an error message. Do NOT use for incident postmortems (use /incident), code review (use /review), or running tests (use /test).Votes: 0GitHub stars: 2
- MigrateFramework and library migration assistant. Detects current usage, identifies the migration path from official docs, generates a migration plan, and applies changes incrementally with testing between steps. Each step is a separate commit for easy rollback. Handles framework migrations, library swaps, major version upgrades, and language version upgrades. Use when user says "migrate", "upgrade", "swap library", "replace express with fastify", "upgrade to v5", "move from jest to vitest", or want...Votes: 0GitHub stars: 2
- Module AuditSurvey a codebase for shallow modules and produce a ranked report of consolidation opportunities. Reads the project glossary if one exists, walks the code looking for interfaces nearly as large as their implementations, applies the deletion test, and recommends consolidations with before-and-after Mermaid diagrams. Use when the user says "audit modules", "find shallow modules", "where is the architecture friction", "consolidate this", or after `/assessment` flagged broad architecture debt. Do...Votes: 0GitHub stars: 2
- MorningCross-account work triage. Sweeps every authenticated GitHub, GitLab, and Bitbucket identity plus the organizations they belong to, finds every pull request, issue, review request, and mention that demands a response, ranks by who is blocked, writes a dated report, then works the queue with per-item consent. Use when user says "morning", "inbox", "triage", "standup", "sweep", "rounds", "daily", "varredura", "what needs my attention", "what is waiting on me", or wants a start-of-day pass acros...Votes: 0GitHub stars: 2
- OnboardOnboard to a new codebase with structured exploration. Scans the project, generates an architecture map with Mermaid diagrams, identifies entry points, explains the tech stack, lists key patterns and conventions, and produces a "start here" guide. Use when user says "onboard", "new project", "understand this codebase", "what does this project do", "walk me through the project", "project overview", or joins a new team or repository. Do NOT use for explaining a single file (use /explain), code ...Votes: 0GitHub stars: 2
- PlanPlan implementations, record architecture decisions, and scaffold boilerplate. Subcommands: plan (default), adr, scaffold. Creates spec folders, manages ADRs, and generates files from existing project patterns. Use when user says "plan this", "how should I implement", "design this feature", "create an ADR", "scaffold a service", "architecture decision", or needs to think through an approach before coding. Do NOT use for code review (use /review), shipping (use /ship), or running tests (use /t...Votes: 0GitHub stars: 2
- Pr SummaryGenerate PR summary with reviewer suggestions based on file ownership. Fetches PR data, summarizes changes, highlights risks, and recommends reviewers from git history. Use when user says "pr summary", "summarize this PR", "who should review this", "generate PR description", or wants a reviewer-ready summary of a pull request. Do NOT use for code review (use /review), creating PRs (use /ship pr), or checking CI status (use /ship checks).Votes: 0GitHub stars: 2
- ProfilePerformance profiling and bottleneck identification. Instruments code to find the slowest operations, ranks by impact, and suggests specific optimizations. Use when user says "profile", "why is this slow", "find bottleneck", "performance issue", "slow query", "slow endpoint", "optimize", or needs to find what is causing poor performance. Do NOT use for benchmark comparisons (use /benchmark), load testing (use /test perf), or general code review (use /review).Votes: 0GitHub stars: 2
- ReadmeGenerate a README and GitHub repo description by analyzing the project's actual codebase, infrastructure, and architecture. Two variants. Marketing (default) for open source and portfolio: hero, badges, highlights grid. Assessment via `--variant assessment` for take-home submissions and architecture audits: technical tone, tables, narrative design decisions. Use when user says "write a README", "generate README", "update README", "repo description", "assessment README", or wants a polished pr...Votes: 0GitHub stars: 2
- RefactorGuided refactoring with behavior preservation verification. Identifies candidates (long functions, deep nesting, duplicated logic, god classes), proposes a refactoring plan, executes incrementally with tests between steps, and verifies no behavior change. Use when user says "refactor", "clean up this code", "simplify", "extract", "restructure", "reduce complexity", "split this file", or wants to improve code structure without changing behavior. Do NOT use for new features (use /plan), bug fix...Votes: 0GitHub stars: 2
- ResearchMulti-source external research with entity resolution, query planning, parallel fan-out, cross-source clustering, and grounded synthesis. Use when user says "research X", "what does the community say about X", "compare X vs Y", "find prior art for X", "market scan for X", "what are people using for X", or asks for a survey of an external domain. Do NOT use for internal codebase questions, use /onboard. Do NOT use for debugging, use /investigate. Do NOT use for code review, use /review.Votes: 0GitHub stars: 2
- ResolveGuided merge conflict resolution with verification. Shows each conflict with context from both branches, suggests resolution based on understanding both changes, verifies tests pass after resolution, and checks that no functionality was lost. Use when user says "resolve conflicts", "merge conflict", "fix conflicts", "rebase failed", "conflict resolution", or has merge conflicts to resolve. Do NOT use for general debugging (use /investigate), code review (use /review), or git workflow questions.Votes: 0GitHub stars: 2
- RespondRespond to incoming code review comments on a PR you authored. Fetches every unresolved comment across all channels, inline threads, review bodies, PR-level conversation, and commit comments, classifies each by author and intent, verifies against the current code, fixes what is real, replies only inside a human's inline thread, closes bot threads and unrepliable channels without a comment, and monitors CI. Use when user says "respond to review", "address comments", "handle reviewer feedback",...Votes: 0GitHub stars: 2
- RetroSession retrospective and codebase pattern discovery. Subcommands: retro (default) extracts corrections and preferences into durable config, discover extracts codebase conventions into rule files. Enhanced with self-improving agent lifecycle. Use when user says "retro", "what did we learn", "save preferences", "discover patterns", "extract conventions", or after a significant multi-step session with corrections worth persisting.Votes: 0GitHub stars: 2
- ReviewReview code, run QA analysis, or audit visual design. Subcommands: code (default), qa, design. Three-pass code review with 71-category checklist, 30-rule QA analysis with PICT and coverage delta, and frontend design/accessibility/performance/SEO audit. Use when user says "review this PR", "review my code", "check this diff", "QA analysis", "test coverage gaps", "design audit", "check accessibility", "check performance", "check SEO", or wants feedback on a specific change. Do NOT use for full ...Votes: 0GitHub stars: 2
- Session LogSession activity logger for handoff and standup. Shows what was done in the current session, including files changed, tests run, commits made, and decisions taken. Use when user says "session log", "what did we do", "session summary", "handoff notes", "standup notes", "export session", or wants a summary of current session activity for handoff or standup prep. Do NOT use for retrospectives (use /retro), checkpoints (use /checkpoint), or morning standup dashboard (use /morning).Votes: 0GitHub stars: 2
- SetupInteractive project environment setup. Reads .env.example, prompts for missing values, detects required services and offers to start them via Docker, runs migrations, seeds the database, and verifies the app starts successfully. Use when user says "setup", "set up the project", "configure environment", "first time setup", "get this running", "initialize", or is setting up a project for the first time. Do NOT use for infrastructure management (use /infra), deployment (use /deploy), or README g...Votes: 0GitHub stars: 2
- ShipShip code through the full delivery pipeline. Subcommands: commit, pr, release, checks, worktree. Handles semantic commits, pull requests with CI monitoring, tagged releases, pipeline diagnosis, and parallel worktree management. Use when user says "commit", "create a PR", "push", "release", "check CI", "pipeline status", "worktree", or wants to move code from working directory to production. Do NOT use for code review (use /review), running tests (use /test), or planning (use /plan).Votes: 0GitHub stars: 2
- Skill NewScaffold a new SKILL.md with the enforced frontmatter and 6-section template, then validate with the skill linter. Use when user says "new skill", "create a skill", "scaffold a skill", or asks to add a slash command. Do NOT use for editing existing skills (use Edit directly), for renaming a skill (use Bash mv + linter), or for deleting a skill (no skill required).Votes: 0GitHub stars: 2
- SpikeBuild a small throwaway artifact that answers exactly one open design question, then delete it. Two routes inside the skill, a runnable terminal program for state, logic, or data-shape questions, and a side-by-side view comparison for presentation questions. Use when the user says "spike this", "build a quick throwaway", "let me play with the model", "try a few visual directions", or wants to de-risk a design choice before committing to it. Do NOT use for production features (use `/plan`), fo...Votes: 0GitHub stars: 2
- TddRed-green-refactor TDD loop for a single behavior. Writes a failing test first, runs it to confirm red, implements minimum code to make it green, then refactors with the test as a safety net. Use when user says "tdd", "test first", "red green refactor", "write the test first", or wants a disciplined test-first cycle. Do NOT use for bulk test backfill (use /test), debugging existing failures (use /investigate), or planning a feature (use /plan).Votes: 0GitHub stars: 2
- TestRun tests, load benchmarks, coverage analysis, linting, and security scanning. Subcommands absorb /perf for HTTP load testing with k6/wrk/hey/ab. Use when user says "run tests", "check coverage", "lint", "benchmark", "load test", "perf test", or wants to execute the project's test suite with results. Do NOT use for QA analysis of test gaps (use /review qa), security auditing (use /audit), or writing test scenarios during planning (use /plan).Votes: 0GitHub stars: 2
- Zoom OutStep back from a narrow code section and place it in its system context. Reads the file, traces callers and callees, identifies the module boundary, names the architectural role, and surfaces hidden coupling. Use when user says "zoom out", "what is this", "where does this fit", "give me context on this code", "what calls this", or feels lost in unfamiliar code. Do NOT use for line-by-line code review (use /review), debugging (use /investigate), or onboarding to a whole repo (use /onboard).Votes: 0GitHub stars: 2