rshade
- 33 skills
- 0 followers
- 9 hours ago last updated
- ▌
- ▌ Finfocus Install · rshade bundleAutomated FinFocus CLI and plugin setup workflow. Use when installing finfocus, setting up plugins for cloud providers, initializing configuration, bootstrapping a new finfocus environment, or onboarding a project for cost analysis. Triggers on: "install finfocus", "setup finfocus", "configure cost analysis", "install plugins", "bootstrap finfocus", "finfocus setup", "add cost tracking", "onboard project", or any task involving initial finfocus installation and environment configuration.
- ▌ Finfocus Routing · rshade bundleConfigure and debug FinFocus intelligent plugin routing. Use when setting up multi-plugin routing, configuring priority and fallback rules, writing pattern matching for resource types, testing route selection, or debugging why a plugin isn't receiving cost queries. Triggers on: "configure routing", "plugin priority", "fallback chain", "route test", "multi-region routing", "pattern matching", "config routes", "plugin selection", "routing config", or any task involving finfocus plugin routing configuration and debugging.
- ▌ Agentic Workflows · rshadeRoute gh-aw workflow design/create/debug/upgrade requests to the right prompts.
- ▌ Finfocus Analyzer Setup · rshade bundleInstall and configure FinFocus as a Pulumi Analyzer for inline cost estimation during pulumi preview. Use when setting up the analyzer, configuring the policy pack, debugging analyzer issues, or enabling zero-click cost estimates in Pulumi workflows. Triggers on: "set up analyzer", "configure analyzer", "install analyzer", "Pulumi preview costs", "inline cost estimates", "policy pack setup", "analyzer integration", "zero-click cost estimation", "analyzer check", or any task involving finfocus Pulumi Analyzer configuration.
- ▌ Finfocus Dev · rshade bundleFinFocus Core development workflow guide for contributors. Use when implementing features, fixing bugs, writing tests, running CI checks, or following project conventions in the finfocus Go codebase. Triggers on: adding CLI commands, writing Go tests, running make targets, debugging CI failures, understanding project structure, or any Go development task within finfocus-core.
- ▌ Agentic Workflow Designer · rshadeConversational skill that interviews users to design new agentic workflows
- ▌ Finfocus Cost · rshade bundleGuide for using FinFocus CLI to analyze cloud infrastructure costs. Use when running projected or actual cost commands, interpreting cost output, configuring Pulumi integration, working with budgets and recommendations, filtering resources, or understanding cost data flows. Triggers on: "run cost analysis", "projected costs", "actual costs", "cost recommendations", "budget health", "Pulumi preview costs", "cross-provider aggregation", "cost filtering", or any task involving finfocus cost estimation and analysis workflows.
- ▌ Finfocus Plugin · rshade bundleGuide for building FinFocus cost plugins using the pluginsdk and gRPC protocol. Use when creating a new plugin, implementing CostSourceService methods, setting up plugin scaffolding, debugging plugin communication, understanding the plugin lifecycle, or working with the recorder reference plugin. Triggers on: "create a plugin", "implement GetProjectedCost", "plugin gRPC", "pluginsdk", "plugin development", "recorder plugin", or any task involving finfocus plugin architecture.
- ▌ Scout · rshade bundleScout Rule — identify the top 3 highest-impact improvement opportunities in files you're already touching. Analyzes entire file content, not just changed lines. Focuses on pre-existing code quality, not PR bugs. Use when preparing a PR, during code review, or after completing a feature.
- ▌ Decide · rshade bundleThree-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.
- ▌ Go Fix · rshade bundleModernize Go code with the rebuilt go fix command in Go 1.26+. Applies safe, version-aware rewrites to newer language and stdlib idioms (interface{} to any, 3-clause loops to range-over-int, min/max, strings.Cut, new(expr), and 20+ more), iterating to a fixed point and verifying the build afterward. Use whenever Go code should be modernized, cleaned up, or made idiomatic — after a go.mod version bump, when old-style or AI-generated patterns accumulate, when migrating callers off deprecated or renamed APIs (go:fix inline directives), when the user mentions go fix or gofix, or to enforce modern idioms as a CI gate. Not for gofmt formatting, dependency upgrades, or go vet bug-finding.
- ▌ Roadmap · rshade bundleStrategic roadmap management for GitHub repositories. Syncs ROADMAP.md with GitHub Issues and labels, bootstraps roadmap files from scratch, runs brainstorming sessions with boundary checking, and provides quick status summaries. Use when managing project planning, syncing roadmap state, or exploring feature ideas.
- ▌ Hadolint · rshade bundleValidate Dockerfiles against best practices for syntax errors, image tagging, package pinning, and shell script issues in RUN commands. Auto-detects hadolint binary or Docker image fallback. Checks project config or falls back to sensible defaults. Use when creating or modifying Dockerfiles, reviewing container images, or catching Dockerfile anti-patterns before building.
- ▌ Lint Fix · rshade bundleDetect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol. Auto-detects Makefile targets, package.json scripts, Go tools, Python tools, and other common linters. Use when fixing linting errors, running validation pipelines, or ensuring code quality before committing.
- ▌ Tech Debt · rshade bundleSystematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.
- ▌ Actionlint · rshade bundleValidate GitHub Actions workflow files for syntax errors, invalid references, and common mistakes. Auto-detects actionlint binary or guides installation. Checks project config or falls back to sensible defaults. Use when creating or modifying GitHub Actions workflows, validating CI/CD pipelines, or catching workflow errors before pushing.
- ▌ Commitlint · rshade bundleValidate commit messages against the Conventional Commits specification. Auto-detects and installs commitlint CLI if missing. Checks project config or falls back to sensible defaults. Use when validating commit messages, preparing PRs, or enforcing commit conventions.
- ▌ Cost Check · rshade bundleGeneric cost estimation for IaC projects. Detects the IaC stack (Pulumi, Terraform) and compatible cost tool (finfocus, infracost), runs cost analysis, flags expensive resources, cost increases, and total cost against configurable thresholds. Produces a terminal summary and COST_CHECK.md report. Use when checking infrastructure costs, reviewing cost impact of changes, or enforcing budget thresholds in CI.
- ▌ Cost Drift · rshade bundleDrift analysis for Pulumi infrastructure costs. Runs finfocus to compare actual vs projected spend, flags drifting resources against configurable thresholds, generates likely-cause explanations with investigation prompts, and tracks drift trends over time. Produces a terminal summary and COST_DRIFT.md report. Use when investigating cost overruns, validating projections against reality, or monitoring spend drift in CI.
- ▌ Shellcheck · rshade bundleValidate shell scripts for syntax errors, common bugs, quoting issues, and portability problems. Auto-detects shellcheck binary or guides installation. Checks project config or falls back to sensible defaults. Use when creating or modifying shell scripts, validating bash/sh files, or catching shell scripting mistakes before committing.
- ▌ Dep Upgrade · rshade bundleSafe systematic dependency upgrade with vulnerability scanning and rollback capability. Detects project ecosystem, audits outdated and vulnerable packages, presents a prioritized upgrade plan, and executes upgrades one at a time with test verification after each. Use when updating dependencies, fixing vulnerability alerts, or performing periodic dependency maintenance.
- ▌ Nix Install · rshade bundleInstall the Nix package manager across platforms with a choice of installer (Determinate Systems or upstream). Detects OS, distro, and environment (including WSL2), verifies any existing installation, performs a platform-appropriate install, enables flakes, and verifies the result. Use when setting up Nix on a new machine, onboarding to a Nix-based project, or troubleshooting a broken Nix installation.
- ▌ Markdownlint · rshade bundleValidate markdown files against formatting standards. Auto-detects and installs markdownlint-cli if missing. Checks project config or falls back to sensible defaults. Supports auto-fix mode. Use when creating or modifying markdown files, validating documentation, or enforcing markdown conventions.
- ▌ Agent Ready Go · rshade bundlePrepares Go applications to work effectively with AI coding agents. Use when setting up a new Go project or retrofitting an existing one to ensure: structured JSON logging (slog/Zap/ZeroLog/Logrus), machine-readable command output, thorough golangci-lint configuration, non-interactive CLI design with --yes flags, structured error handling with meaningful exit codes, proper context.Context propagation, graceful shutdown, health check endpoints, and a standardized Makefile. Triggers when a user asks to make their Go app "agent-ready," "AI-friendly," wants to improve agent tooling/observability in a Go project, or needs to audit an existing Go project against agent-readiness best practices.
- ▌ Security Audit · rshade bundleComprehensive security audit covering OWASP Top 10, secrets detection, supply chain security, threat modeling, and language-specific vulnerability patterns. Investigates actual code paths rather than grep-matching keywords. Generates a scored SECURITY_AUDIT.md with prioritized remediation. Use when assessing application security, preparing for a security review, or onboarding to a codebase with security concerns.
- ▌ Go Nolint Audit · rshade bundleAudit Go nolint directives for staleness and lazy justifications. Mechanically verifies each suppression with golangci-lint, then runs adversarial Red/Blue/White debates on the top candidates for removal. Use when inheriting a Go codebase, during periodic cleanup, or when nolint count is growing unchecked.
- ▌ Design Principles · rshade bundleAudit a codebase against well-known software design principles: SOLID, DRY, YAGNI, KISS, Law of Demeter, Separation of Concerns, Composition over Inheritance, and the code-relevant 12-Factor subset. Scores findings by impact and effort, runs adversarial debate on contested violations, and generates a prioritized DESIGN_AUDIT.md. Use when reviewing code quality beyond what linters catch, assessing design health before a refactor, or onboarding to an unfamiliar codebase. Can be invoked standalone or delegated from tech-debt.
- ▌ Nix Devshell Init · rshade bundleScaffold a reproducible Nix devShell for a project. Detects project language(s) from sentinel files (go.mod, package.json, pyproject.toml, Cargo.toml), generates a flake.nix with appropriate packages and tooling, creates an .envrc for direnv integration, and verifies the shell builds. Use when onboarding to a project that needs reproducible dev dependencies, adding Nix to an existing repo, or setting up a new project with pinned tooling.
- ▌ Tailscale Install · rshade bundleInstall and configure Tailscale across platforms. Detects OS, distro, and environment (including WSL2 and containers). Verifies existing installations, performs platform-appropriate install, and guides initial connection. Use when setting up Tailscale on a new machine, onboarding a server to a tailnet, or verifying an existing install.
- ▌ Tailscale Docker Debug · rshade bundleDiagnose Tailscale connectivity and DNS failures inside Docker containers. Detects userspace vs kernel mode, DNS resolver conflicts, TUN interface issues, and multi-tailnet mismatches. Use when Tailscale peers connect by IP but MagicDNS names fail, or when containers fall back to userspace networking unexpectedly. Also use when a customer deploys Tailscale in Docker or Podman and reports DNS not working, or when migrating from docker run to docker compose breaks TUN functionality.
- ▌ Pull Request Msg With Gh · rshade bundleGenerate a PR_MESSAGE.md file from session context using GitHub CLI. Detects related issues via branch-keyword search, writes a structured PR description with commit subject, summary, test plan, and changelog. Validates with commitlint and markdownlint. Use when preparing a pull request on GitHub.
- ▌ Tailscale Subnet Router Debug · rshade bundleDiagnose Tailscale subnet router connectivity failures. Traces the full route lifecycle: advertisement, approval, client acceptance, policy routing (table 52), and IP forwarding. Use when clients can reach Tailscale peers by IP but not devices on advertised subnets, or when subnet routes appear approved but traffic doesn't flow. Also use when Docker containers fail to advertise routes, when `ip route` shows no subnet route (it's in table 52), or when traffic flows one way but responses don't return.