rshade

Modernize 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.

Prepares 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.

Validate 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.

Validate 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.

Validate 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.

Strategic 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.

Generate 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.

Audit 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.

Infer JSON structure and types with jq-based schema discovery.

Install 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.

Automated 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.

Configure 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.

FinFocus 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.

Guide 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.

Guide 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.

Guide the operator through deploying the fleet.json-declared workflow set to a tracked repository using the gh-aw-fleet CLI. Use this skill whenever the user says "deploy to <repo>", "run fleet deploy for X", "push fleet workflows to X", "sync workflows to X via fleet", "apply default profile to X", or asks to update agentic workflows on a specific tracked repo. Also trigger when the user names one of the tracked repos (in fleet.json or fleet.local.json) in the same breath as deploy/push/apply/ship verbs. The skill handles dry-run review, the --apply go-ahead gate, and gracefully recovers from gpg-signing failures by composing a manual-finish shell paste rather than bypassing commit signing. Do not trigger for template catalog refreshes (that's fleet-eval-templates), onboarding a brand-new repo (fleet-onboard-repo), bumping pin refs (fleet-upgrade-review), or editing fleet.json structure.

Audit pin health and upgrade readiness across the gh-aw-fleet tracked repositories, then guide targeted upgrades. Use this skill whenever the user says "audit the fleet", "which repos need upgrading", "check pin health", "run fleet upgrade audit", "upgrade all repos", "what's out of date", "run gh aw upgrade across the fleet", or asks about the health of deployed agentic workflows across multiple repos. Also trigger on phrases like "is <repo> up to date" or "any repos behind on their pins". The skill runs `fleet upgrade --audit --all`, presents a per-repo dashboard, and handles individual repo upgrades one at a time with dry-run review and gpg-failure handling. Do not trigger for deploying new workflows (fleet-deploy), for refreshing the upstream catalog (fleet-eval-templates), or for onboarding a new repo (fleet-onboard-repo).

Aggregate per-repo api-consumption-report output across the fleet and recommend where to look for cost concentration. Use this skill whenever the user says "what's our fleet spending", "where is the cost concentrated", "which workflows are burning credits", "consumption rollup", "budget review", "cost by profile", "cost by cost-center", "monthly fleet usage", "what's the top burner", "any spend hotspots", or asks about Copilot-credit usage across multiple repos. Also trigger when the user asks "should we cut anything from `<profile>`" or "is `<repo>` pulling its weight" — both questions resolve to a consumption rollup grouped on the relevant axis. The skill runs `gh-aw-fleet consumption` with the right temporal and group-by flags, reads the structured output, and frames the result as a budget conversation (where the spend is, what's driving it, what to consider next). Do not trigger for deploying or bumping workflows (that's `fleet-deploy` / `fleet-upgrade-review`), for evaluating which upstream workflows to

Refresh the upstream template catalog (templates.json) and evaluate new or changed workflows against fleet profiles. Use this skill whenever the user says "check for new agentic workflows", "what's new in gh-aw or agentics", "refresh the template catalog", "evaluate new workflows", "run template fetch", "any new workflows worth adding", or "what changed upstream". Also trigger when the user asks about the upstream template catalog in general — additions, removals, or fit assessments. The skill runs `template fetch`, reads the resulting JSON in-chat (no subprocess LLM needed — the catalog stores full frontmatter + body), and recommends which new workflows deserve profile inclusion, which are niche, and which are internal/test noise. Do not trigger for deploying workflows to a repo (that's fleet-deploy), for pin-health auditing (that's fleet-upgrade-review), or for onboarding a new repo (fleet-onboard-repo).

Add a new repository to the gh-aw-fleet tracked set and walk it through its first deploy. Use this skill whenever the user says "add repo X to fleet", "track X with gh-aw-fleet", "onboard X", "start managing X", "register X in the fleet", "include X in our fleet", or provides a repo spec that isn't already in fleet.json / fleet.local.json and wants it managed. Also trigger if the user says "deploy to X" but X is not yet tracked — pivot to this skill before attempting deploy. The skill edits fleet.local.json to register the repo (never fleet.json, which is the public example), asks for profile selection and per-repo customization (engine override, exclusions, extras), verifies via `go run . list`, and then hands off to fleet-deploy for the first PR. Do not trigger for already-tracked repos (that's fleet-deploy), for fleet-wide audits (fleet-upgrade-review), or catalog evaluation (fleet-eval-templates).

Scaffold a new fleet profile — add a `profiles.<name>` entry to fleet.json (or fleet.local.json) with a curated workflow list and pinned source refs, and optionally mirror it to `profiles/<name>.json`. Use this skill whenever the user says "build a profile", "create a profile", "scaffold a profile", "new profile", "add a profile to fleet.json", "make a profiles/<name>.json", "start a docs-plus / security-plus / quality-plus / community-plus profile", or proposes a named profile that doesn't exist yet. Also trigger when `fleet-eval-templates` has surfaced candidates the user now wants materialized into a profile definition. The skill reads `templates.json` for workflow metadata, proposes the profile JSON inline, writes on approval, and for the `default` profile mirrors both files to preserve the documented verbatim-match invariant. Do not trigger for evaluating upstream workflows (that's `fleet-eval-templates`), for deploying an existing profile to a repo (that's `fleet-deploy`), for rotating pins on already-d

Use this skill for any task that changes — or reacts to a change in — a project's github.com/rshade/ax-go dependency, even when it looks routine; don't do it by hand instead. Trigger it when someone bumps, updates, or upgrades github.com/rshade/ax-go (aka ax-go, the agentic-experience lib) in go.mod — by hand, via go get -u, or a renovate/dependabot PR; moves ax-go from one version to another, including old versions and multi-minor jumps; sees staticcheck SA1019 deprecation warnings on ax.* symbols after updating ax-go; hits a compile error like 'undefined: ax.NewID' after updating; or finds the ax.Error envelope or __schema output changed shape after a bump. It reads the module's own CHANGELOG breaking notes and //Deprecated: notes, applies each documented migration, and verifies the build and tests stay green. Do NOT use it for developing ax-go itself, scaffolding a new CLI on ax-go, upgrading a different dependency in an ax-go project, or general questions about ax-go.