rheged-studio

@rheged-studio source repo

10 skills
0 followers
7 hours ago last updated

▌
Scaffold New Skill · rheged-studio bundle
Generate a spec-compliant new-skill skeleton under skills/<name>/ for the agent-skills repo, so new bundles start consistent and stop drifting. Use when asked to scaffold / create / bootstrap / start a new skill, add a new skill bundle, or generate the boilerplate for a skill. Writes a SKILL.md, a package.json (@rheged-studio/skill-<name>, private, version 0.1.0), a config.json + config.example.json with identical key sets, an entry script wired to the standard --help / --dry-run / --self-test dispatch idiom, a vitest test stub, and a README — all passing the same pnpm validate:skills gate. Has a --dry-run preview and refuses to clobber an existing bundle.

0
installs
▌
Commit · rheged-studio bundle
Turn the working tree into logical, atomic Conventional Commits — classify uncommitted files as in-scope vs out-of-scope against the branch's merge base, show a staging plan, and create one commit per coherent unit (type + optional scope + British-English body; `!` / `BREAKING CHANGE:` for breaking changes). Never `git add -A`; files that look like they belong to another branch/worktree are never staged silently. Use when asked to commit uncommitted work, tidy WIP into atomic commits, or as the commit step inside a ship flow (e.g. `/send-it`). It commits only — no push, PR, changelog, or Linear writeback.

0
installs
▌
Send It · rheged-studio bundle
The all-in-one ship pipeline — commit uncommitted work, run the change-gated lint preflight, author the dated changelog entry, compose a Conventional Commits PR title, push, open or update a PR, move linked Linear issues to In Review, then chain into `triage-pr` (Step 11) to drive the PR to merge-ready. Incomplete until Step 11 has run, or `--skip-triage` / `triage: false` was used with a stated reason. Use when asked to ship, send it, finish a branch, open or update a PR, or wrap up and push. Thin orchestrator over `commit`, `preflight`, `changelog`, `linear-sync`, and `triage-pr`; owns branch guard, release-type decision, PR title, push, and PR. Serves monorepos and single-package repos alike.

0
installs
▌
Changelog · rheged-studio bundle
Author, refresh, or repair the changelog entry for the current branch — derive metadata, write the frontmatter and grouped body, run the deterministic enrichment scripts, and validate against the changelog contract. Use when asked to write or update a changelog entry, refresh an entry after new commits, or as the changelog step inside a ship/PR flow. Detects an existing entry for the branch (idempotent update-vs-create), keeps `created_at` sacred, leaves post-merge fields to the release step, and validates with a zero-dependency Node script.

0
installs
▌
Preflight · rheged-studio bundle
Run a change-gated, branch-scoped lint preflight (ESLint / markdownlint / actionlint) on the files a branch changes versus its base, classify each violation as introduced vs pre-existing, and drive the fix/defer loop via an exit-code contract (0 pass, 1 introduced/blocking, 2 pre-existing only). Use when asked to run preflight, check whether a branch will pass lint before pushing, or as the lint gate inside a ship/PR flow. Lints only the categories the branch touched — not a whole-repo lint — with linted workspaces and the base branch auto-detected, so a consuming repo configures nothing in the common case.

0
installs
▌
Triage Pr · rheged-studio bundle
Drive a pull request from draft with failing CI to merge-ready. While the PR is a draft, inspect and fix in-scope CI failures (lint, manifest-lint, build, tests) using the gh CLI and GitHub Actions logs — never weakening CI config to greenwash, and never editing lint config or adding an ignore directive unprompted (those are gated for the developer's sign-off and reported, not applied). After the PR is marked ready-for-review, wait for AI reviewers, verify each finding, then — by default — halt for a human envelope before applying dispositions (accept / decline / create a follow-up issue); with --auto-apply, fix high-impact findings and file the rest as follow-ups as before. Use when asked to triage a PR, fix failing CI or red checks on a PR, address or respond to PR review comments, action Bugbot or Claude review feedback, get a PR green, or take a draft PR to merge-ready. Handles base-branch drift and in-scope merge conflicts; escalates ambiguous ones.

0
installs
▌
Linear Sync · rheged-studio bundle
Transition the Linear issues linked to the current branch through their workflow states (In Progress / In Review / Done) — resolve live state IDs by team name, extract issue IDs from the branch, and apply the transition idempotently. Use when starting work on an issue, when a PR opens or updates, during branch cleanup, or whenever a branch's Linear issues need their state synced. Resolves state IDs by team name (not key — keys go stale on rename), reads the team name and issue-ID prefixes from config.json, and skips any issue already at or past the target state.

0
installs
▌
Cleanup Repo · rheged-studio bundle
Clean up a Git repository's merged branches and worktrees, then prune filesystem cruft (recursively-empty directories and orphaned node_modules). Use when asked to clean up / tidy / prune merged branches, remove stale or finished worktrees, delete branches whose PRs have already merged (including squash-merges), or sweep empty directories and leftover node_modules. Two-pass merge detection (git ancestry plus merged GitHub PRs), an uncommitted-changes guard on worktrees, an optional Linear "Done" writeback, per-pass confirmation gates, and a --dry-run preview. Protected branches are never touched.

0
installs
▌
Release Status · rheged-studio bundle
Diagnose the release-please release pipeline, read-only. Preview the next version from Conventional-Commit subjects on commits since the last tag (feat→minor, fix/perf/revert→patch, !/BREAKING→major; docs/chore/ci/refactor/ test/build/style→none; merge commits excluded), show the open release-please--branches--main PR and its required-check (GO/NO GO) status, detect the recurring stale `autorelease: pending` stall on the last merged release PR (where release-please aborts and releases silently stop firing), and confirm tag-vs-version parity (does a v<package.json version> tag already exist, or is publishing pending — the release.yml version-vs-tag gate). Use when asked why a release didn't fire, what version would cut next, whether the release PR is green, whether the pipeline is stalled, or to check release health. Advisory only — it inspects post-merge main and changes nothing.

0
installs
▌
Initialise Skills · rheged-studio bundle
Scan the host repo a set of agent skills is installed into and reconcile every installed skill's config.json with detected facts — base branch, monorepo package roots, changelog directory, Linear issue-key prefixes, review bots, protected branches — plus the Linear team name and workspace slug fetched via the Linear MCP. Use when first installing these skills into a repo, or to refresh the configs after the skill set or repo layout changes. Also emits a committed `.claude/skills.lock` inventory of installed skill versions, and ensures the preflight skill's `.preflight-summary.json` scratch output is gitignored, and strips erroneous consumer rules that gitignore skill `config.json` (A-812). Idempotent and safe to re-run: it reconciles drift rather than clobbering deliberate manual edits, presents a dry-run diff first, and only writes after confirmation — preserving each config's key order and formatting so a no-op run leaves files byte-identical.

0
installs

10 published skills