caveman
claudeTalk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
The CI/CD planner: inventory, map, calculate, contain, write, prove. Calculated, not controlling.
Plugin rio from marketplace rio in yunst047/rio-skills. Commands read from the repo's manifest — 13 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
rio-containerRio's container plan — build Docker/OCI images in CI and deploy them to Kubernetes. Covers image build modes (Docker-in-Docker with TLS, socket binding, rootless BuildKit/Buildah), buildx caching and multi-arch, tagging and deploy-by-digest, registry auth (GitLab registry, GHCR, ECR, GAR, ACR), imag
rio-planRio's CI/CD plan — before any YAML, lay out the whole delivery system: inputs, outputs and stakeholders at each step, the DevOps user journey from commit to production or store, a multi-repo streamline plan (shared templates, downstream triggers, artifact contracts), and the pipeline schedule plan (
rio-releaseRio's release plan — ship builds from CI to Google Play, the App Store / TestFlight, Firebase App Distribution, and web/backend deployment platforms (Kubernetes, Cloud Run, ECS, Vercel, Netlify) through their APIs and integration tools, with fastlane as the default for mobile (match, gym, supply, pi
rio-runnerRio's runner plan — choose and configure CI runners/agents: executor type (shell, Docker executor, Kubernetes executor, docker-autoscaler, VM, macOS hosts), runner settings (concurrency, tags, protected/locked, cache, privileged, pull policy, ephemeral), and multi-runner planning (pools per workload
rio-secretsRio's variables and credentials plan — where each CI variable lives and who can read it (project/group/org, environment-scoped, protected, masked, file-type), and how the pipeline authenticates to cloud platforms: OIDC / workload identity federation first, then short-lived vault tokens, then scoped
rio-terraformRio's infrastructure-as-code pipeline — run Terraform / OpenTofu through CI safely: fmt/validate/lint/security scan, plan on every MR/PR with the plan shown to reviewers, apply only the saved, reviewed plan on main behind an approval, one apply per state at a time, remote state with locking (S3, GCS
rio-verifyRio's verification plan — wire test frameworks into the pipeline and validate the running system: test placement and fail-fast order, JUnit/coverage reports surfaced in the MR/PR, post-deploy smoke tests and health checks, and mobile E2E device handling — Android emulators (KVM) and iOS simulators i
rio-ymlRio's pipeline YAML — write or refactor CI configuration with minimal redundancy: job declaration, templates and reuse (extends, anchors, includes, reusable workflows, shared libraries), linear stage sequencing, parallel jobs and needs/DAG dependencies, matrix fan-out, concurrency that never kills a
rioTsukatsuki Rio mode — the Seminar President who plans CI/CD before a single line of YAML. A cold, precise DevOps planner: inventories inputs, outputs and stakeholders, maps the pipeline flow, calculates critical path and runner cost, contains secrets and concurrency, writes minimal DRY pipeline YAML
/rio:rio-containerBuild Docker images in CI and deploy them to Kubernetes — build mode, registry, Helm/GitOps, rollback.
/rio:rio-helpQuick reference for Rio levels, skills, and commands.
/rio:rio-planPlan the CI/CD system — stakeholders, flow, DevOps journey, multi-repo, schedules.
/rio:rio-releasePlan and automate releases — Play Store, App Store/TestFlight, fastlane, deploy targets.
/rio:rio-runnerPlan runners — executor choice, settings, multi-runner pools and capacity.
/rio:rio-secretsPlan CI variables and cloud auth — scope, protection, OIDC, signing material.
/rio:rio-terraformRun Terraform / OpenTofu through CI — plan on MR, apply the saved plan, state, OIDC, drift.
/rio:rio-verifyWire tests and runtime validation into CI — reports, emulators, simulators, devices.
/rio:rio-ymlWrite or refactor pipeline YAML — DRY jobs, stages/needs, concurrency, artifacts, dropdowns, schedules.
/rio:rioSet Rio intensity (memo / seminar / big-sister / off). No arg = the default.
command -v node >/dev/null 2>&1 && node "${CLAUDE_PLUGIN_ROOT}/hooks/rio-activate.js" || exit 0
command -v node >/dev/null 2>&1 && node "${CLAUDE_PLUGIN_ROOT}/hooks/rio-mode-tracker.js" || exit 0
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.