← all publishers

karotkriss

@karotkriss source repo

11 published skills

  1. Caffeinated Whale Design · karotkriss bundle
    Use this skill to generate well-branded interfaces and assets for Caffeinated Whale (the cwcli CLI and Caffeinated Whale Desktop), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for protoyping.
    0
    installs
  2. Caffeinated Whale Design 2 · karotkriss
    Use this skill to generate well-branded interfaces and assets for Caffeinated Whale (the cwcli CLI and Caffeinated Whale Desktop), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
    0
    installs
  3. Remove Background · karotkriss
    Remove the background from an image (or a whole folder of images), producing a transparent-background PNG cutout. Runs the rembg segmentation model locally and offline via uvx - no API key, no rate limits, no anti-bot, full resolution. Use whenever the user wants to remove, erase, delete, strip, or knock out an image background; cut out a subject; make a photo/logo/product background transparent; create a PNG cutout or sticker; or asks for remove.bg-style background removal.
    0
    installs
  4. Glab Axi · karotkriss
    Operate GitLab through the glab-axi CLI - issues, merge requests, CI/CD pipelines, projects, labels, CI/CD variables and secrets, releases, search, and raw API access. Use whenever a task touches GitLab: listing or filing issues, reviewing or merging merge requests, checking pipeline status and failed job logs, managing CI/CD variables and secrets, cutting releases, or querying the GitLab API.
    0
    installs
  5. Glab Axi Release · karotkriss
    Cut a glab-axi release: move the CHANGELOG Unreleased section to a new version, bump package.json, tag, create the GitHub release (which publishes to npm), and verify the publish landed. Use when releasing glab-axi, publishing a new glab-axi version to npm, or preparing a glab-axi release.
    0
    installs
  6. Cwcli · karotkriss
    Manage local Frappe/ERPNext Docker instances through the cwcli CLI - list instances, start/stop/restart them, check per-process health, back up and unlock sites, manage bench apps, and search cached apps and sites. Use whenever a task touches a local Frappe or ERPNext development instance, bench, or site: checking whether an instance is running, starting or restarting one, backing up or restoring a site, installing or updating bench apps, or finding which bench holds an app or site.
    0
    installs
  7. Cwcli Release · karotkriss
    How to cut a cwcli (caffeinated-whale-cli) release - the exactly-four version-bump files (pyproject.toml, __init__.py, uv.lock, CHANGELOG.md), the CHANGELOG Keep-a-Changelog format, the semver convention this repo practices, the develop -> vX.Y.Z tag publish path, the uv publish PyPI flow in release.yml (the UV_PUBLISH_TOKEN prerequisite, --check-url non-reproducible-build gotcha, why the old pypa action was replaced), the hand-written release-card copy the workflow requires before it will publish, and the isolated release-to-tap fan-out that bumps the karotkriss/homebrew-cwcli Homebrew formula. Use this whenever you bump the cwcli version, edit CHANGELOG.md for a release, write a release note, publish to PyPI, touch the Homebrew tap bump job, or touch .github/workflows/release.yml, .github/scripts/release-body.sh, .github/release-notes/, or build.yml.
    0
    installs
  8. Cwcli Lifecycle · karotkriss bundle
    Incident-level root-cause internals of cwcli's lifecycle and destructive commands - init (Frappe/bench version gating, admin/db-root secret env-transport, existing-bench reuse flow), rm (what deletion actually removes, conf/-only archive, recache-under-spinner deadlock, the C1/H5/M11 backup+name+exit-code data-safety gates, multi-bench per-bench backup, the start-back-up-delete transient-start flow for a stopped project), and restore (receive-mode and normal-path data-safety, non-interactive selectors, secrets off the argv, streamed copies, shared site detection, default-site resolution, post-restore migrate+restart), and start/stop/status/logs/restart (the supervisord per-process supervision substrate: PID-keyed idempotency, config/launcher generation, per-process logs, the stdout-token-only status contract, single-program restart + auto-heal). Use this whenever you edit or debug core/init.py, commands/init.py, core/rm.py, commands/rm.py, core/restore.py, commands/restore.py, commands/start.py, commands/stat
    0
    installs
  9. Cwcli Apps Update · karotkriss
    Incident-level internals of cwcli's apps command group (list/install/uninstall/update/checkout) and the update state machine - multi-site fan-out by default, --json stdout purity, post-mutation recache, git-URL app-name derivation, the deprecated `cwcli update` alias and its frappe special-case, list/install/uninstall on the logic core (core/apps.py: the untangled uninstall consent/auto_start, report.ok-driven exit codes, `cwcli axi apps list`, `axi apps checkout`, and `axi apps install` shipping while `axi apps uninstall` stays deferred, and how the checkout and install absence assertions were each reversed), and core/update.py's control flow plus maintenance-mode safety (why it is NOT a generator, why a lost stream is unknown-not-failed, per-site enable/disable, honest partial-failure exit codes, shlex-quoted interpolation). Use this whenever you edit or debug commands/apps.py, core/apps.py, commands/update.py, core/update.py, or `axi apps list`/`axi apps update`, or touch app install/uninstall/update/check
    0
    installs
  10. Cwcli E2e Testing · karotkriss
    End-to-end testing protocol for cwcli against real Frappe/ERPNext Docker instances - the isolation recipe (CWCLI_HOME or a temp HOME, the cwe2e- project prefix, dedicated volumes/network), building genuine v14/v15/v16 benches instead of fixtures, driving interactive prompts through a real pty (the ESC[?2004h raw-mode marker), driving non-interactive paths with flags, teardown, and the tests/e2e/harness.py contract. Use this whenever you write, run, or extend E2E tests (anything under tests/e2e/), touch tests/e2e/harness.py, or hand-validate a cwcli behavior change on a real instance - even if the task just says "test it on a real instance" without naming E2E.
    0
    installs
  11. Cwcli Inspect Benches · karotkriss
    Incident-level internals of cwcli's inspect / cache / multi-bench layer - inspect's 3-tier freshness model (T1 serve-cache / T2 read-only partial drift-check / T3 full re-cache), the multi-bench addressing model (numeric vs durable user labels, the --bench selector, marker-file recovery), the shared --yes / auto-start / honest-exit-code contract, the cache secret-redaction whitelist that keeps secrets out of the SQLite cache, and the CWCLI_HOME on-disk footprint override. Use this whenever you edit or debug core/inspect.py, commands/inspect.py, commands/label.py, utils/bench_labels.py, utils/db_utils.py, utils/config_utils.py, the SQLite cache, or anything touching multi-bench selection / labels. Each note guards a real shipped bug - keep the root-cause "why".
    0
    installs