jyje

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Deploy a group of raw Kubernetes manifests via GitOps/ArgoCD without an underlying application chart, using the manifest-group shell chart. Use when a set of resources (ConfigMap, CRD instance, Ingress, RBAC, Job, etc.) needs to live in its own ArgoCD Application/namespace but doesn't belong to any existing Helm release.

Pull a Helm chart from a repo (or OCI) at a specific version and save it under helm/<group>/ with a versioned directory name. Use when adding or upgrading a vendored Helm chart, when the user asks to vendor a chart, or when following the repo's "add chart to helm/" workflow.

ensure all Helm charts have 'extraResources' support by patching templates/extra-resources.yaml and values.yaml. Run when searching for root charts or when a new chart is added.

Update LiteLLM proxy configuration by translating AI SDK example code (Python/shell) into litellm.yaml model entries. Use when the user provides sample code using NVIDIA NIM, OpenAI, or other AI provider SDKs and wants to add the model to the cluster's LiteLLM proxy.

Enroll a namespace into Istio Ambient Mesh by adding an explicit Namespace resource with the istio.io/dataplane-mode=ambient label via extraResources in the representative ArgoCD Application. Use when the user asks to add a namespace to ambient mesh, enable ambient mode for a namespace, or apply istio.io/dataplane-mode=ambient to a namespace via GitOps.

Lint Resume and Portfolio web and print-preview layouts for wrapped content rows. Use when editing resume or portfolio data, Liquid templates, or SCSS; when the user asks to check line wrapping, one-line layout, print layout, portfolio layout, or resume-lint.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Import and optimize a source image into the blog assets directory, generating responsive JPG variants following the project's naming convention. Use when adding a new blog post image or thumbnail.

Run Jekyll production build to match CI (GitHub Actions). Use when verifying SCSS/layout changes before push, debugging CI-only build failures, or when the user asks to check production build.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Keep the chart's "Environment variables" README section (charts/hermes-agent/README.md.gotmpl) in sync with upstream Hermes Agent's supported env vars at the currently pinned appVersion. Use after an image version bump (cron-fetch-image PR), periodically, or when asked to check/update/audit Hermes env vars.

Run the AI-assisted release proposal flow for this chart end-to-end via gh CLI — trigger propose-release, review the PR, adjust the version, watch CI, and merge. Use when the user asks to cut/propose/ship a release, check on a release PR, or change its version.

Format a README's header as a centered hero block (title, optional logo, tagline, badges, language links) matching the style jyje uses across his own repos. Use when creating a new README from scratch, or asked to restyle/center an existing one.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Lint, format, and type-check Python code with ruff and ty, then run pytest, before considering any Python change done. Use whenever Python source files are added or edited in a uv-managed project.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Run ruff and ty to lint and type check the FastAPI backend project. Use this when the user requests to check the backend code quality or type safety.

Format a README's header as a centered hero block (title, optional logo, tagline, badges, language links) matching the style jyje uses across his own repos (ansible, presentation, hermes-agent-helm, ...). Use when creating a new README from scratch, or asked to restyle/center an existing one.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Build and maintain a persistent, compounding markdown wiki from sources. Use for incremental knowledge-base ingest/query/lint workflows.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.

Generate descriptive commit messages by analyzing git diffs following the project's specific policy. Use when the user asks for help writing commit messages or reviewing staged changes.