@copado/agentia-cli 0.93.0-alpha.0 → 0.94.0-alpha.0

package/oclif.manifest.json

@@ -30,12 +30,36 @@
           "allowNo": false,
           "type": "boolean"
         },
+        "force-skills": {
+          "description": "Replace unmanaged files at Agentia skill paths",
+          "name": "force-skills",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "no-prompt": {
           "char": "n",
           "description": "Skip interactive prompts; only run checks, notifications, and flagged actions",
           "name": "no-prompt",
           "allowNo": false,
           "type": "boolean"
+        },
+        "setup-skills": {
+          "description": "Create or update Agentia-managed project skills and AGENTS.md guidance",
+          "name": "setup-skills",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "skills-target": {
+          "description": "Skill target root (repeatable)",
+          "name": "skills-target",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "options": [
+            "agents",
+            "cursor",
+            "claude"
+          ],
+          "type": "option"
         }
       },
       "hasDynamicHelp": false,
@@ -5211,6 +5235,50 @@
         "update.js"
       ]
     },
+    "cicd:user:get": {
+      "aliases": [],
+      "args": {},
+      "description": "Get a Copado user by ID (defaults to the authenticated user)",
+      "examples": [
+        "<%= config.bin %> <%= command.id %>",
+        "<%= config.bin %> <%= command.id %> --id me",
+        "<%= config.bin %> <%= command.id %> --id 005000000000000",
+        "<%= config.bin %> <%= command.id %> --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "id": {
+          "description": "User ID, or \"me\" for the authenticated user",
+          "name": "id",
+          "default": "me",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "cicd:user:get",
+      "pluginAlias": "@copado/agentia-cli",
+      "pluginName": "@copado/agentia-cli",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "isESM": true,
+      "relativePath": [
+        "dist",
+        "commands",
+        "cicd",
+        "user",
+        "get.js"
+      ]
+    },
     "cicd:work:commit": {
       "aliases": [],
       "args": {
@@ -6561,10 +6629,10 @@
           "type": "boolean"
         },
         "target": {
-          "description": "Project skill root to write",
+          "description": "Project skill root to write (repeatable)",
           "name": "target",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "options": [
             "agents",
             "cursor",
@@ -6640,10 +6708,10 @@
           "type": "boolean"
         },
         "target": {
-          "description": "Project skill root to write",
+          "description": "Project skill root to write (repeatable)",
           "name": "target",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "options": [
             "agents",
             "cursor",
@@ -13359,50 +13427,6 @@
         "unresolve.js"
       ]
     },
-    "cicd:user:get": {
-      "aliases": [],
-      "args": {},
-      "description": "Get a Copado user by ID (defaults to the authenticated user)",
-      "examples": [
-        "<%= config.bin %> <%= command.id %>",
-        "<%= config.bin %> <%= command.id %> --id me",
-        "<%= config.bin %> <%= command.id %> --id 005000000000000",
-        "<%= config.bin %> <%= command.id %> --json"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "id": {
-          "description": "User ID, or \"me\" for the authenticated user",
-          "name": "id",
-          "default": "me",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "cicd:user:get",
-      "pluginAlias": "@copado/agentia-cli",
-      "pluginName": "@copado/agentia-cli",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "isESM": true,
-      "relativePath": [
-        "dist",
-        "commands",
-        "cicd",
-        "user",
-        "get.js"
-      ]
-    },
     "cicd:work:deployment-step:create": {
       "aliases": [],
       "args": {},
@@ -14119,5 +14143,5 @@
       ]
     }
   },
-  "version": "0.93.0-alpha.0"
+  "version": "0.94.0-alpha.0"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@copado/agentia-cli",
   "description": "Command-line interface for Agentia",
-  "version": "0.93.0-alpha.0",
+  "version": "0.94.0-alpha.0",
   "author": "Copado Solutions",
   "bin": {
     "agentia": "./bin/run.js"

package/templates/AGENTS.md

@@ -0,0 +1,24 @@
+# Agentia CLI for AI Agents
+
+<!-- agentia:managed:start -->
+
+Use Agentia to manage Copado work items. Prefer registered Agentia MCP tools; otherwise use the CLI with `--json`.
+
+Authentication must be configured before operational commands. Never print credentials, tokens, or unmasked environment variables.
+
+## Copado workflow
+
+`list → get → set → commit → push → submit → done`
+
+Read records before changing them and use IDs returned by Copado. Do not skip `work set` before coding; use one story per feature branch. Keep the working tree clean for lifecycle commands, and confirm promotion/deployment intent before `done`.
+
+## Agent Skills
+
+Load exactly one copy of each applicable Agentia skill. Prefer the client-specific root when available (`.cursor/skills` in Cursor or `.claude/skills` in Claude); otherwise use `.agents/skills`.
+
+- `agentia-cicd/SKILL.md`: Copado stories, commits, push, submit, done, promotions, jobs, environments, pipelines, and data.
+- `agentia-testing/SKILL.md`: Copado Robotic Testing operations.
+- `agentia-ai/SKILL.md`: Copado AI operations.
+
+Project rules in this file take precedence over managed skill guidance. Refresh managed skills with `agentia setup skills update`; do not hand-edit managed files.
+<!-- agentia:managed:end -->

package/templates/skills/agentia-cicd/references/data.md

@@ -6,6 +6,75 @@ Use this reference for Release Data Template commands under `agentia cicd data .
 
 Data commands often accept large JSON bodies. Prefer `--file` or `--stdin` for complex payloads and `--json` for machine-readable responses.
 
+## Operating Rules
+
+- Read the target template, credential, User Story, or data commit before mutating it.
+- Use IDs returned by Copado. Do not infer template, credential, commit, or ContentVersion IDs.
+- Use `data sobject fields` and `data sobject relationships` before constructing payloads that reference Salesforce fields or relationships.
+- For JSON payload commands, use exactly one input source: inline JSON flags, `--file`, or `--stdin`.
+- Prefer `--file` when a payload should be reviewed, edited, or reused. Prefer `--stdin` for generated, one-use payloads.
+- After every mutation, read the affected resource back or run its corresponding `list` command.
+
+## Choose A Workflow
+
+| Intent | Workflow |
+| --- | --- |
+| Find or export an existing template | Inspect A Template |
+| Test source records and destination matching | Validate Records And Matching |
+| Update templates after metadata changes | Synchronize Metadata Changes |
+| Attach data to a User Story and inspect generated files | Create A Data Commit |
+| Convert or remove a template | Legacy Conversion And Deletion |
+
+## Inspect A Template
+
+1. Discover candidates with `data template list --json`.
+2. Inspect the selected-column graph with `data template get <template-id> --json`.
+3. Use `data template get-detail <template-id> --json` only when raw v2 configuration is needed for editing or troubleshooting.
+4. Inspect attached filters and formulas with `data filter list` and `data formula list` when relevant.
+
+Finish when the correct template and its current configuration have been identified. Keep `get-detail` output as a baseline before changing template detail.
+
+## Validate Records And Matching
+
+1. Inspect the template and source/destination credentials.
+2. Search representative source records with `data records search`.
+3. Match selected source records against the destination with `data records match`.
+4. Review unmatched or ambiguous results.
+5. Adjust filters or formulas when needed, then repeat the search and match checks.
+
+Treat this as a feedback loop. Finish when representative records produce the intended source selection and destination matches.
+
+## Synchronize Metadata Changes
+
+1. Prepare the metadata-change request in a JSON file.
+2. Run `data sync preview-updates --file <preview-request> --json`.
+3. Review every preview entry, especially `needsAttention` and `autoUpdate`.
+4. Build an apply payload containing only approved sync entries.
+5. Run `data sync apply --file <sync-entries> --json`.
+6. Read each affected template back to verify its fields and relationships.
+
+Never apply preview results without reviewing them first. Stop for user input when an entry needs attention and the intended field change is unclear.
+
+## Create A Data Commit - Full template
+
+1. Resolve and inspect the target User Story; see [work.md](work.md).
+2. Inspect the selected template and credentials.
+3. Prepare the data commit request in a JSON file.
+4. Run `data commit create --file <commit-request> --json`.
+5. If the response contains a JobExecution ID, inspect and monitor it using [jobs.md](jobs.md).
+6. Confirm the commit is attached to the intended story with `data commit list <user-story-id> --json`.
+7. List generated artifacts with `data dataset-file list <data-commit-id> --json`.
+8. Fetch required content with `data dataset-file content <content-version-id>`.
+
+Finish when the data commit belongs to the intended story, any returned job has reached the expected status, and generated dataset files are accounted for.
+
+## Legacy Conversion And Deletion
+
+1. Discover and inspect the exact template.
+2. Save its `get` and `get-detail` output before conversion or deletion.
+3. For legacy conversion, run `data template convert-old <template-id> --json`, then read the converted template back.
+4. For deletion, confirm the target and destructive intent before running `data template delete <template-id> --json`.
+
 ## Template Commands
 
 | Command | Use For | Notes |
@@ -60,6 +129,6 @@ agentia cicd data dataset-file list <data-commit-id> --json
 ## Gotchas
 
 - Template IDs, credential IDs, data commit IDs, and ContentVersion IDs are different values. Read the parent record before using child commands.
-- JSON payload commands should use exactly one input source: inline JSON flags, `--file`, or `--stdin`.
 - `data template get` and `data template get-detail` serve different audiences: selected graph export versus raw v2 detail.
 - `data template open` is CLI-only; MCP covers data operations but not browser navigation.
+- A data commit can hand off to a CICD JobExecution. Continue with `agentia cicd job ...`, not CRT `agentia testing job ...`.