All authors

Claude Skills by IsaiaScope
github.com/IsaiaScope16 skills0 installs19 views
- Hetzner CreateProvision a new hardened Hetzner VPS end to end. Sets up the local toolchain if missing (hcloud CLI, API context, SSH keypair, ssh_config Include), then creates the server with the firewall attached and cloud-init hardening applied at first boot, verifies SSH comes up on the non-standard port, and registers it in the fleet roster. Use when invoked as /hetzner-create <name>, or when asked to "create a VPS", "provision a Hetzner server", "spin up a new box", or "set up a new server".Votes: 0GitHub stars: 2
- Hetzner DeleteDestroy a Hetzner VPS safely and clean up everything it leaves behind. Refuses protected servers, shows the full blast radius, takes a snapshot first, requires the server name typed out to confirm, then deletes and sweeps the orphans it leaves in the fleet roster, ssh config, known_hosts, and Hetzner-side resources. Use when invoked as /hetzner-delete <name>, or when asked to "delete a VPS", "destroy a server", "tear down a box", or "decommission a server".Votes: 0GitHub stars: 2
- Hetzner SshConnect to a Hetzner VPS over SSH and end up in a position to actually work on it. Reads the fleet roster at ~/.config/hetzner/hetzner.json, unlocks the ed25519 key from the macOS keychain, opens a multiplexed connection to a hardened host (key-only, non-standard port), verifies it is the right box, and hands back a live socket for subsequent commands. Use when invoked as /hetzner-ssh [server], or when asked to "get into the VPS", "ssh into the server", "connect to Hetzner", or to start worki...Votes: 0GitHub stars: 2
- Hetzner UpdateAlign the version of a self-hosted open-source app between your Mac and a Hetzner VPS, upgrading whichever side is behind. Reads the software registry at ~/.config/hetzner/hetzner.json, compares both halves, classifies every release in between as safe or breaking, and stops for approval before crossing a breaking change. Takes a database backup before touching the server and verifies from the server's own logs afterwards. Use when invoked as /hetzner-update [app], or when asked to "update mul...Votes: 0GitHub stars: 2
- Iso Ai InitInitialize AI defaults. Global steps run anywhere — install/verify caveman (ultra + shrink + statusline) and shrink any allowlisted MCP server that is present and stdio-launchable. Repo-scoped steps (graphify CLI install + /graphify wiring) run only inside a git repo. A gate decides which steps apply. Use when the user runs /iso-ai-init or asks to set up AI tooling.Votes: 0GitHub stars: 2
- Iso BrowserDrive a browser the user is already signed into, reusing a tab they have open or opening a new one, instead of an isolated profile that is logged out of everything. Detects and configures whichever agent is installed — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Zed, Codex or any other — then verifies the CDP connection and reads and fills real pages. Use when invoked as /iso-browser [status|agents|doctor|setup|launch], when browser automation lands on a login wall, when a tool re...Votes: 0GitHub stars: 2
- Iso CommitWrite a commit message and commit. Conventional Commits subject (type(scope): message), body is a plain dot list of what the work does — only when the subject doesn't already cover it. No Co-Authored-By, no AI attribution, no LLM filler. Stages everything by default; --staged commits the index only. Use when invoked as /iso-commit [--staged] [--split], or when the user asks to commit / write a commit message.Votes: 0GitHub stars: 2
- Iso ConfigRead and check the Iso config that every iso-* skill uses — branch vocabulary, paths, tracker, terminal, identity. Two scopes merged per key: ~/.config/iso/iso.json describes you, docs/iso/config.json describes one repo. Use when invoked as /iso-config [init|show|doctor], when a skill reports a missing or wrong config value, or when setting up iso-* skills on a new machine.Votes: 0GitHub stars: 2
- Iso Init RepoSet up a repo with IsaiaScope governance defaults — GitHub repo creation, prod/test/dev branch structure with protection, and branch-gate CI enforcing the cascade order. Use when the user runs /iso-init-repo or asks to set up repo governance.Votes: 0GitHub stars: 2
- Iso Issue TrackingRecord agent work on the work tracker every iso-* skill files against. The iso-* chain drives the ticket at its own boundaries — /iso-plan opens it, /iso-write moves it, /iso-push closes it with a retro — and you open or bind rows by hand for work with no plan behind it. Use when a request changes something durable inside a git repo. Inert outside a repo.Votes: 0GitHub stars: 2
- Iso PlanPlanning-only chain. Runs brainstorming → grilling → (prototype, only when needed) → writing-plans in order, then renders a visual summary of the finished plan file. Inside a repo the grill step uses grill-with-docs and halts if setup-matt-pocock-skills has not been run; outside a repo it uses grill-me. No state, no implementation. Use when the user runs /iso-plan, optionally with a seed idea as the argument.Votes: 0GitHub stars: 2
- Iso PushPush committed work, open a PR against dev, and land it with a merge commit so no commit is ever rewritten or duplicated. Use when invoked as /iso-push [--pr] [--cascade test|prod] [--no-merge] [--stay], or when asked to push a branch, open a PR against dev, or promote dev to test or prod. Requires a dev or develop branch on origin. Rebases the branch onto its base automatically; returns to dev after a landing unless --stay; never force-pushes without explicit approval.Votes: 0GitHub stars: 2
- Iso ReadmeWrite or refine README files in the IsaiaScope house style — curated shieldcn (shadcn-styled) badges, context-aware layout (repo root/app · skill · lib/pkg), scannable prose — then commit only the README changes and push. Global, stack-agnostic (node, python, rust, go, docs-only, monorepo). Use when invoked as /iso-readme [path], or asked to write/refine/beautify a README in my style.Votes: 0GitHub stars: 2
- Iso ReviewTake the work sitting on this branch and make it better, then check it. Three phases, in one order: | # | phase | what it asks | runs | |---|---|---|---| | 1 | architecture | is this the right shape? | here, in this session | | 2 | simplify | can this read plainer? | here, in this session | | 3 | review | is this wrong? | a subagent | Invocation: `/iso-review [--no-architecture] [--no-simplify] [--no-review]`. All three run by default. Mechanics live in `skills/iso-review/scripts/review.sh`. ...Votes: 0GitHub stars: 2
- Iso SpawnSpawn a codex or claude agent in its own herdr tab inside the SAME workspace where the skill runs, with full permissions and an optional auto-running prompt. Use when the user wants to spawn/open/launch a codex or claude tab/agent/panel in the current herdr workspace, dispatch a task to a sub-agent beside the current session, or says "spawn codex", "open a claude tab", "/iso-spawn", "launch an agent here".Votes: 0GitHub stars: 2
- Iso WriteImplement a written plan using TDD, without committing. Use when invoked as /iso-write <plan_path> [--no-branch | --branch=<name> | --worktree] or handed an implementation plan to build. By default it resumes or cuts a branch derived from the plan filename only when the current branch is a base branch (dev, develop, test, prod, main, master) or detached, and otherwise stays on the feature branch already checked out; --no-branch always implements on the current branch; --branch=<name> uses a n...Votes: 0GitHub stars: 2