Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

JKamsker

@jkamsker source repo

5 published skills

  1. ▌
    Gitea Ops · jkamsker bundle
    Work with Gitea instances via the tea CLI and a bundled REST-backed PowerShell toolkit — issues, labels, milestones, pull requests, comments, Actions runs, failure logs, and workflow dispatch. Use for any repo whose remote is a Gitea host, when tea hangs in a non-interactive shell, or when Gitea Actions CI needs diagnosing. Not for Forgejo (use forgejo-ops) or GitHub (use gh).
    0
    installs
  2. ▌
    Forgejo Ops · jkamsker bundle
    Work with Forgejo instances (self-hosted, Codeberg) through the fj and fj-ex CLIs instead of hand-rolled curl — PRs, issues, releases, Actions runs, full CI log download, artifacts, cancel/rerun, workflow dispatch, and secrets. Use for any repo whose remote is a Forgejo host, when CI fails on Forgejo Actions, or when fj argument-order errors appear ("unexpected argument found"). Not for Gitea (use gitea-ops) or GitHub (use gh).
    0
    installs
  3. ▌
    Forge Detect · jkamsker bundle
    Reliably distinguish which software forge a host or git remote points at — Forgejo, Gitea, GitHub, or GitLab — including sub-path installs and locked-down (REQUIRE_SIGNIN_VIEW) instances. Use before picking forge tooling (fj/fj-ex vs tea vs gh vs glab), when a repo's remote host is unfamiliar, or when someone asks "is this Gitea or Forgejo?". Ships tested detection scripts for bash and PowerShell.
    0
    installs
  4. ▌
    Build Ergonomic Clis · jkamsker bundle
    Designs, reviews, and implements product-grade command-line interfaces. Covers command tree structure, flag conventions, auth and profile UX, config precedence, human-first output defaults with opt-in machine output (--json), confirmation and dry-run rules, exit codes, and non-interactive behavior. Use when designing a CLI, reviewing CLI UX/DX, planning command structure, adding argument parsing, or implementing a service CLI. Supports C#/.NET Spectre.Console.Cli and Rust clap.
    0
    installs
  5. ▌
    Incremental Source Generator · jkamsker bundle
    Design, review, debug, and fix Roslyn incremental source generators. Use when creating or modifying `IIncrementalGenerator` implementations, diagnosing incorrect or missing generated code, improving incrementality or IDE performance, adding marker attributes or analyzer-config/MSBuild inputs, inspecting emitted `.g.cs` output, or adding tests and packaging for source generators and analyzers.
    0
    installs