@kolatts/pncli 1.26.0 → 2.0.0

package/dist/{config-SQ3YHJHI.js → config-YHYQTGKT.js}

@@ -4,19 +4,21 @@ import {
   loadConfig,
   loadJsonFile,
   maskConfig,
+  normalizeBaseUrl,
   setConfigValue,
   setRepoConfigValue,
   writeGlobalConfig,
   writeRepoConfig
-} from "./chunk-JOAWUILY.js";
+} from "./chunk-PXKUQPPF.js";
 export {
   getGlobalConfigPath,
   loadConfig,
   loadJsonFile,
   maskConfig,
+  normalizeBaseUrl,
   setConfigValue,
   setRepoConfigValue,
   writeGlobalConfig,
   writeRepoConfig
 };
-//# sourceMappingURL=config-SQ3YHJHI.js.map
+//# sourceMappingURL=config-YHYQTGKT.js.map

package/dist/{http-WCDXXCKQ.js → http-6QJU2SWP.js}

@@ -2,9 +2,10 @@
 import {
   HttpClient,
   createHttpClient
-} from "./chunk-AGELHQKO.js";
+} from "./chunk-ZDJYOI3W.js";
+import "./chunk-HZF6WQPU.js";
 export {
   HttpClient,
   createHttpClient
 };
-//# sourceMappingURL=http-WCDXXCKQ.js.map
+//# sourceMappingURL=http-6QJU2SWP.js.map

package/dist/output-XT3WT5L5.js

@@ -0,0 +1,24 @@
+#!/usr/bin/env node
+import {
+  debug,
+  fail,
+  isDebugEnabled,
+  log,
+  setGlobalOptions,
+  setGlobalUser,
+  success,
+  warn,
+  writeRawOutput
+} from "./chunk-HZF6WQPU.js";
+export {
+  debug,
+  fail,
+  isDebugEnabled,
+  log,
+  setGlobalOptions,
+  setGlobalUser,
+  success,
+  warn,
+  writeRawOutput
+};
+//# sourceMappingURL=output-XT3WT5L5.js.map

package/dist/output-XT3WT5L5.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolatts/pncli",
-  "version": "1.26.0",
+  "version": "2.0.0",
   "description": "The Paperwork Nightmare CLI — One command does what three meetings couldn't.",
   "type": "module",
   "bin": {

package/skills/pncli/SKILL.md

@@ -9,7 +9,9 @@ metadata:
   services: config
 ---
 
-pncli gives AI agents and humans unified CLI access to enterprise tools: Jira, Bitbucket, Confluence, SonarQube, SDElements, Azure DevOps, Jenkins, Artifactory, IBM UrbanCode Deploy, Checkmarx, ServiceNow, Contrast Security IAST, Sonatype IQ Server, OpenShift / Kubernetes, Dynatrace, and LogScale.
+pncli gives AI agents and humans unified CLI access to enterprise tools: Jira, Bitbucket, Confluence, SonarQube, SDElements, Azure DevOps, Jenkins, Artifactory, Checkmarx, ServiceNow, Contrast Security IAST, Sonatype IQ Server, OpenShift / Kubernetes, Dynatrace, LogScale, and Figma.
+
+Every service authenticates the same way: a personal access token you generate in that tool's own UI and put in an env var or the config file. If a tool you need is missing from the table below, it is not out of scope by default — pncli covers enterprise tooling broadly, and the only hard requirement is personal-access-token auth.
 
 ## Two config levels
 
@@ -47,7 +49,6 @@ For detailed setup of any service, read the included file for that service.
 | SonarQube | `sonarqube.md` | Code quality issues |
 | SDElements | `sde.md` | Threat model tasks |
 | Checkmarx | `checkmarx.md` | SAST findings |
-| IBM UrbanCode Deploy | `udeploy.md` | Component versions, deployments |
 | Jenkins | `jenkins.md` | Builds, job status |
 | Artifactory | `artifactory.md` | Packages, repos |
 | ServiceNow | `servicenow.md` | Change requests, incidents |
@@ -56,6 +57,8 @@ For detailed setup of any service, read the included file for that service.
 | OpenShift / Kubernetes | `openshift.md` | Pod health, events, logs, metrics |
 | Dynatrace | `dynatrace.md` | Services, entities, problems, traces, Kubernetes workloads |
 | LogScale | `logscale.md` | Log queries, repository listing |
+| Split.IO | `splitio.md` | Feature flag discovery, targeting updates, Change Requests |
+| Figma | `figma.md` | Design files, comments, version history |
 | Skills Marketplace | `marketplace.md` | Install org-internal skills |
 
 ## Setup walkthrough

package/skills/pncli/figma.md

@@ -0,0 +1,62 @@
+# Figma
+
+pncli uses the Figma REST API directly; no external CLI is required.
+
+## Configuration
+
+| Key | Environment variable | Purpose |
+|---|---|---|
+| `figma.baseUrl` | `PNCLI_FIGMA_BASE_URL` | Figma API base URL — always `https://api.figma.com` |
+| `figma.token` | `PNCLI_FIGMA_TOKEN` | Personal access token |
+
+Generate a personal access token in Figma under **Account Settings → Personal access tokens**.
+
+```bash
+pncli config set figma.baseUrl https://api.figma.com
+pncli config set figma.token <your-token>
+pncli config test
+```
+
+## Finding a Figma file key
+
+The file key is the alphanumeric segment in a Figma URL. Both URL formats are accepted:
+
+```
+https://www.figma.com/design/ABCDEFGH1234/My-Design-Name
+                              ^^^^^^^^^^^^
+https://www.figma.com/file/ABCDEFGH1234/My-Design-Name
+                            ^^^^^^^^^^^^
+```
+
+You can pass either the raw file key or the full URL to any `figma` command.
+
+## Commands
+
+```bash
+# Get current user — useful for verifying credentials
+pncli figma me
+
+# Get file metadata and structure summary (component and style counts)
+pncli figma file ABCDEFGH1234
+pncli figma file "https://www.figma.com/design/ABCDEFGH1234/My-Design"
+
+# Include the full document node tree (can be large)
+pncli figma file ABCDEFGH1234 --document
+
+# Get all comments on a file
+pncli figma comments ABCDEFGH1234
+
+# Get comments as of a specific point in time
+pncli figma comments ABCDEFGH1234 --as-of 2026-08-01T00:00:00Z
+
+# Get version history
+pncli figma versions ABCDEFGH1234
+
+# List files in a Figma project (project ID is visible in the project URL)
+pncli figma project-files 123456789
+```
+
+## Notes
+
+- `figma file` returns a summary by default: name, last-modified, version, thumbnail URL, role, editor type, schema version, and counts of components and styles. Pass `--document` to include the full document node tree (this can be very large for complex designs).
+- Passing a Figma image (screenshot or export) rather than a link is **not supported** — pncli works with the Figma REST API only, not image analysis. Use the file key or URL instead.

package/skills/pncli/jenkins.md

@@ -49,3 +49,50 @@ pncli config set --repo defaults.jenkins.baseUrl https://jenkins.myteam.imagile.
 ```
 
 Resolution order (highest to lowest): project `.pncli.json` → global config → `PNCLI_JENKINS_BASE_URL` env var.
+
+## Multiple Jenkins instances
+
+When you work with more than one Jenkins controller (e.g. a stable production instance plus ephemeral pipeline-as-code instances), add a `jenkinsInstances` array to your global config:
+
+```json
+{
+  "jenkinsInstances": [
+    {
+      "name": "prod",
+      "baseUrl": "https://jenkins.imagile.dev",
+      "username": "you@example.com",
+      "apiToken": "abc12345"
+    },
+    {
+      "name": "ephemeral",
+      "baseUrl": "https://jenkins-tmp.imagile.dev",
+      "username": "you@example.com",
+      "apiToken": "abc12345"
+    }
+  ]
+}
+```
+
+Manage the array with the `instance` subcommands, which append rather than replace:
+
+```
+pncli jenkins instance add --name prod --base-url jenkins.imagile.dev --username you@example.com --api-token abc12345
+pncli jenkins instance add --name ephemeral --base-url jenkins-tmp.imagile.dev --username you@example.com
+pncli jenkins instance list
+pncli jenkins instance remove --name ephemeral
+```
+
+Omit `--api-token` on an interactive terminal and pncli prompts for it, which keeps the token out of your shell history. `instance list` masks every token as `***`. Adding a name that already exists is rejected unless you pass `--force`, which overwrites that entry in place.
+
+`pncli config set jenkinsInstances '[...]'` also works, but it **replaces** the whole array — you must re-supply every instance you want to keep, including tokens that `config check` masks. Prefer `instance add`.
+
+Then select an instance at run-time with `--instance`:
+
+```
+pncli jenkins --instance ephemeral pipeline list
+pncli jenkins --instance prod pipeline run --name my-job --wait
+```
+
+When `--instance` is omitted, pncli uses the default `jenkins.*` config as usual.
+
+**Note:** Per-instance credentials are read only from the global config file — there is no env-var override for a named instance. To override Jenkins credentials at runtime (CI/CD, GitHub Actions), use the default `jenkins.*` config with `PNCLI_JENKINS_BASE_URL`, `PNCLI_JENKINS_USERNAME`, and `PNCLI_JENKINS_API_TOKEN`, and omit `--instance`.

package/skills/pncli/openshift.md

@@ -85,6 +85,27 @@ pncli openshift pod-metrics --namespace my-namespace
 Returns per-pod, per-container CPU and memory usage. Requires the metrics-server to be
 installed in the cluster (`GET /apis/metrics.k8s.io/v1beta1/...`).
 
+### Get combined resource usage, limits, and requests
+
+```bash
+pncli openshift resource-usage --namespace my-namespace
+pncli openshift resource-usage --namespace my-namespace --label-selector app=my-app
+pncli openshift resource-usage --namespace my-namespace --csv
+```
+
+Fetches pod specs (limits/requests) and metrics-server usage in parallel, joins them by
+pod + container, and normalizes all values to **millicores (m)** for CPU and **mebibytes (Mi)**
+for memory. Pods without metrics (e.g. not Running) appear with empty usage columns.
+
+Use `--csv` to emit a spreadsheet-ready CSV suitable for Excel:
+
+```
+Pod,Container,CPU Usage (m),Memory Usage (Mi),CPU Limits (m),Memory Limits (Mi),CPU Requests (m),Memory Requests (Mi)
+my-pod-abc,app,45,128,500,256,100,128
+```
+
+Requires the metrics-server (`GET /apis/metrics.k8s.io/v1beta1/...`) — same as `pod-metrics`.
+
 ## Test connectivity
 
 ```bash
@@ -93,7 +114,8 @@ pncli config test
 
 ## Minimum RBAC permissions
 
-The service account needs read access to pods, events, logs, and metrics in the target namespace:
+The service account needs read access to pods, events, logs, and metrics in the target namespace.
+`resource-usage` requires the same metrics-server permission as `pod-metrics`:
 
 ```yaml
 rules:

package/skills/pncli/splitio.md

@@ -0,0 +1,178 @@
+# Split.IO
+
+pncli uses the Split Admin API v2 directly; no external CLI is required.
+
+## Configuration
+
+| Key | Environment variable | Purpose |
+|---|---|---|
+| `splitio.baseUrl` | `PNCLI_SPLITIO_BASE_URL` | Split Admin API base URL, such as `https://api.split.io` |
+| `splitio.adminApiKey` | `PNCLI_SPLITIO_ADMIN_API_KEY` | Admin API key generated in the Split UI |
+
+Generate an Admin API key in the Split UI under **Admin Settings → API Keys → Admin**.
+
+```bash
+pncli config set splitio.baseUrl https://api.split.io
+pncli config set splitio.adminApiKey <your-admin-api-key>
+pncli config test
+```
+
+## Change Controls
+
+Every write command submits a **Change Request** (CR) rather than modifying flag definitions directly. Each CR requires:
+
+| Flag | Required | Description |
+|---|---|---|
+| `--mnemonic` | Yes | Short title for the CR (appears in the Split UI) |
+| `--description` | Yes | Longer description of the intent |
+| `--change-number` | Yes | ServiceNow change ticket (e.g. `CHG0001234`) |
+| `--approvers` | Situational | Comma-separated Split user IDs for non-production approvals |
+| `--yes` | Optional | Skip interactive confirmation (for CI/CD pipelines) |
+
+All write commands prompt for confirmation unless `--yes` is supplied. The `--dry-run` flag prints the request body without sending it.
+
+## Commands
+
+### Discovery
+
+```bash
+# List all workspaces
+pncli splitio workspaces list
+
+# List environments in a workspace
+pncli splitio environments list --workspace <wsId>
+
+# List feature flags in a workspace (paginated)
+pncli splitio flags list --workspace <wsId>
+pncli splitio flags list --workspace <wsId> --limit 100 --offset 0
+pncli splitio flags list --workspace <wsId> --flag-set my-flag-set
+```
+
+### Inspect
+
+```bash
+# Get a flag's global definition (treatments, traffic type, tags)
+pncli splitio flags get --workspace <wsId> --flag my-feature
+
+# Get a flag's full definition including targeting rules for one environment
+pncli splitio flags get --workspace <wsId> --flag my-feature --environment <envId>
+```
+
+### Update (full definition replacement)
+
+Provide the complete flag definition as JSON via `--input-file`. Use `pncli splitio flags get --environment` to retrieve the current definition before editing it.
+
+```bash
+pncli splitio flags update \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --mnemonic "SPLIT-001" --description "Enable feature for all users" \
+  --change-number CHG0001234 --approvers "user-id-1,user-id-2" \
+  --input-file definition.json
+```
+
+The file must contain the full definition object (treatments, rules, defaultRule, etc.).
+
+### Change one rule
+
+```bash
+# Route all traffic in rule 0 to one treatment
+pncli splitio flags set-rule \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --rule-index 0 --treatment on \
+  --mnemonic "SPLIT-002" --description "Route beta users to on" \
+  --change-number CHG0001234
+
+# Weighted distribution for rule 1
+pncli splitio flags set-rule \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --rule-index 1 --weights '[{"treatment":"on","size":80000},{"treatment":"off","size":20000}]' \
+  --mnemonic "SPLIT-003" --description "80/20 split for rule 1" \
+  --change-number CHG0001234
+```
+
+### Change default rule
+
+```bash
+pncli splitio flags set-default \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --treatment off \
+  --mnemonic "SPLIT-004" --description "Default traffic to off" \
+  --change-number CHG0001234
+```
+
+### Kill and restore
+
+```bash
+# Kill a flag (forces all traffic to the default treatment)
+pncli splitio flags kill \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --mnemonic "SPLIT-005" --description "Emergency kill for incident INC0001234" \
+  --change-number CHG0001234 --yes
+
+# Restore a killed flag
+pncli splitio flags restore \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --mnemonic "SPLIT-006" --description "Restore after incident resolved" \
+  --change-number CHG0001234
+```
+
+### Archive a flag
+
+```bash
+pncli splitio flags archive \
+  --workspace <wsId> --flag my-old-feature \
+  --mnemonic "SPLIT-007" --description "Flag is fully rolled out, cleaning up" \
+  --change-number CHG0001234
+```
+
+### Toggle a single flag
+
+```bash
+# Disable
+pncli splitio flags toggle \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --enabled false \
+  --mnemonic "SPLIT-008" --description "Disable for maintenance" \
+  --change-number CHG0001234
+
+# Enable
+pncli splitio flags toggle \
+  --workspace <wsId> --flag my-feature --environment <envId> \
+  --enabled true \
+  --mnemonic "SPLIT-009" --description "Re-enable after maintenance" \
+  --change-number CHG0001234
+```
+
+### Batch-toggle from a file
+
+Failures do not stop remaining entries. Each flag creates its own Change Request.
+
+```bash
+# toggles.json:
+# [
+#   { "flag": "feature-a", "enabled": false },
+#   { "flag": "feature-b", "enabled": true }
+# ]
+
+pncli splitio flags batch-toggle \
+  --workspace <wsId> --environment <envId> \
+  --mnemonic "SPLIT-010" --description "Maintenance window toggles" \
+  --change-number CHG0001234 --yes \
+  --input-file toggles.json
+```
+
+### Change Request tracking
+
+```bash
+# List all CRs for a workspace
+pncli splitio change-requests list --workspace <wsId>
+
+# Filter by environment and status
+pncli splitio change-requests list --workspace <wsId> \
+  --environment <envId> --status REQUESTED
+
+# Retrieve a specific CR
+pncli splitio change-requests get --id <crId>
+```
+
+**Valid status values:** `REQUESTED`, `APPROVED`, `REJECTED`, `PUBLISHED`