@copado/agentia-cli 0.85.0-alpha.0 → 0.86.0-alpha.0

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

@@ -0,0 +1,84 @@
+<!-- Agentia managed skill file: agentia setup skills -->
+
+# CICD Work Reference
+
+Use this reference for `agentia cicd work ...` and matching MCP tools such as `agentia_work_get`, `agentia_work_commit`, `agentia_work_push`, `agentia_work_submit`, and `agentia_work_done`.
+
+## Workflow
+
+1. Discover: `agentia cicd work list --assigned-to-me --json`
+2. Inspect: `agentia cicd work get <id-or-name> --json`
+3. Activate: `agentia cicd work set <id-or-name> --json`
+4. Implement and choose one commit path:
+   - Local Git: `agentia cicd work commit --local --all --json`
+   - Copado cloud metadata: `agentia cicd work commit <story-id> --cloud --metadata-name <name> --metadata-type <type> --metadata-category SFDX --json`
+5. Register local commits: `agentia cicd work push --json`
+6. Validate and submit: `agentia cicd work submit --json`
+7. Promote only on explicit approval: `agentia cicd work done --json`
+
+`work set`, `work push`, `work submit`, and `work done` expect a clean tracked working tree and the active story context recorded by `work set`.
+
+## Core Commands
+
+| Command | Use For | Notes |
+| --- | --- | --- |
+| `work list` | Find candidate stories | Use `--assigned-to-me`, `--status`, `--project-name`, `--name`, pagination flags. |
+| `work get [ID]` | Read story details | ID is optional after `work set`. Human output redacts OAuth signatures; JSON preserves structured fields. |
+| `work create` | Create a story | Use `--title`, project/team/assignee/theme fields, specs, and short acceptance criteria. |
+| `work update [ID]` | Mutate story fields or status | ID is optional after `work set`. Acceptance criteria must be fewer than 255 chars. |
+| `work set ID` | Mark active and prepare branch | Fetches base branch, creates/checks out `feature/<story-name>`, stores local context. |
+| `work commit` | Local or cloud commit | `--local` is default; `--cloud` calls Copado commit APIs and can poll a job. |
+| `work push` | Push local commits and register with Copado | Requires active story context and clean tree. Sends stored retrieve-only permissions. |
+| `work test --local` | Run local quality gate scripts | Runs `.agentia_quality_gates.sh` or `.agentia_quality_gates.cmd` from repo root. |
+| `work submit` | Submit for review/validation | Runs local gates unless `--skip-local-tests`; can push ahead commits. |
+| `work done` | Promote after approval | Pushes if needed, then promotes without validate-only behavior. |
+| `work promote` | Story-centric promotion run | Requires `--cloud`; use `--deploy` for merge and deploy. |
+| `work status [ID]` | Check story and related executions | Useful after submit, done, promote, or commit jobs. |
+| `work open [ID]` | Open story in browser | CLI-only browser helper. |
+
+## Local Commit Path
+
+Use local commits for normal source changes:
+
+```sh
+agentia cicd work commit --local --all --permissions CustomField:Account.SLA__c,ApexClass:AccountService --json
+agentia cicd work push --json
+```
+
+`--permissions` records metadata that Copado should treat as Retrieve Only during push. List the metadata the permissions point at, not the permission set or profile files themselves. The value is sticky in local user config until replaced or cleared with `--permissions ""`.
+
+`--apex-test-classes` records story-related test class names for later reference. `work test --local` and `work submit` still take `--apex-test-classes` explicitly when you want the local gate script to receive them.
+
+## Cloud Commit Path
+
+Use cloud commits when Copado should retrieve metadata itself:
+
+```sh
+agentia cicd work commit <story-id> --cloud --message "Commit AccountService" --metadata-name AccountService --metadata-type ApexClass --metadata-category SFDX --json
+agentia cicd work commit <story-id> --cloud --file commit-request.json --json
+```
+
+For Salesforce metadata, include `--metadata-category SFDX`. Without the SFDX category, Copado deploy logs can report "Salesforce changes not found."
+
+## Deployment Steps
+
+Deployment steps are attached to a user story and run during promotion.
+
+| Command | Use For |
+| --- | --- |
+| `work deployment-step types` | List supported standard/custom step types. |
+| `work deployment-step salesforce-flows` | List directly invocable Salesforce Flows. |
+| `work deployment-step list` | Inspect current story steps. |
+| `work deployment-step create` | Add Manual Task, Salesforce Flow, Function, Apex, Data Set, Data Template, or Robotic Test steps. |
+| `work deployment-step update` | Apply sparse step updates. |
+| `work deployment-step reorder` | Submit a complete before/after ordering snapshot from file or stdin. |
+| `work deployment-step delete` | Delete an owned step by ID. |
+
+Prefer explicit flags for standard step types. Use `--config-json`, `--file`, or `--stdin` only when the step has expert configuration not covered by flags. Read `types` first when unsure.
+
+## Gotchas
+
+- `work test --local` is not CRT. For Robot Framework execution, use the `agentia-testing` skill.
+- `work submit` and `work done` may push ahead commits, but `work set` is still required first.
+- `work done` promotes/deploys. Do not run it unless the user explicitly asked to promote or finish the story.
+- `work delete` is destructive; read the story and confirm intent first.

package/templates/skills/agentia-testing/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: agentia-testing
+description: Use this skill when creating, updating, running, inspecting, or troubleshooting Copado Robotic Testing tests with the Agentia CLI, especially commands under `agentia testing test`, CRT projects, robots, jobs, builds, logs, variables, PAT authentication, Git-backed test storage, and Robot Framework execution.
+---
+
+<!-- Agentia managed skill file: agentia setup skills -->
+
+# Agentia Testing
+
+Use this skill to operate Copado Robotic Testing through Agentia without confusing CRT projects, robots, jobs, tests, and builds.
+
+Prefer Agentia MCP tools when they are available and match the task. Use CLI examples as the fallback, and add `--json` whenever the result will be parsed or reused.
+
+## Start Here
+
+1. Confirm CRT auth with `agentia auth get --crt --json`, or provide `--pat`, `--domain`, and `--org` on the command.
+2. Identify or create the CRT Project and Robot before creating or running tests.
+3. Use `testing test ...` as the canonical namespace for test workflows. The shorter `testing run|logs|status|create|update` forms exist for compatibility.
+4. Never expose PATs, organization secrets, or generated log content that contains secrets.
+
+## Reference
+
+- CRT test creation, updates, execution, status, logs, and related project/robot/job/build prerequisites: [references/tests.md](references/tests.md)
+
+## General Rules
+
+- `agentia testing test run` starts CRT Robot Framework execution. It is different from `agentia cicd work test --local`.
+- `agentia testing job` manages CRT job/test definitions. It is different from `agentia cicd job`, which manages Copado CICD JobExecution records.
+- Use `--wait-for-result` on `testing test run` when the agent must return the final build result in one turn.
+- Use Git-backed job flags only when the user or project clearly uses repository-backed CRT test storage.
+
+## Report Back
+
+Report the CRT project, robot, job/test ID, build ID when present, final status, and where logs were written or fetched. Do not include PATs or other secrets.

package/templates/skills/agentia-testing/references/tests.md

@@ -0,0 +1,65 @@
+<!-- Agentia managed skill file: agentia setup skills -->
+
+# CRT Testing Reference
+
+Use this reference for `agentia testing test ...` and related Copado Robotic Testing commands.
+
+## Authentication And Context
+
+Configure CRT once:
+
+```sh
+agentia auth set --crt --crt-domain <domain> --crt-org <organization-id>
+agentia auth get --crt --json
+```
+
+Most CRT commands also accept per-command `--pat`, `--domain`, and `--org` overrides. Do not print PAT values.
+
+## Canonical Test Workflow
+
+1. List or create a project: `agentia testing project list --json`
+2. List or create a robot: `agentia testing robot list --json`
+3. Create or update a test: `agentia testing test create ... --json`
+4. Run the test: `agentia testing test run <job-id> --project <project-id> --wait-for-result --json`
+5. Inspect status and logs: `agentia testing test status ... --json` and `agentia testing test logs ... --json`
+
+## Test Commands
+
+| Command | Use For | Notes |
+| --- | --- | --- |
+| `testing test create` | Create a CRT test and upload Robot files | Requires project, robot, name, and `--file` or `--dir`. |
+| `testing test update ID` | Update files for a test | Use `--add`, `--remove`, `--replace`, or Git branch options. |
+| `testing test run ID` | Run a CRT test | Use `--project`; use `--wait-for-result` when the final status is required. |
+| `testing test status` | List build/run status | Filter by project, job, and status. |
+| `testing test logs ID` | Fetch build logs | Use `--project`, `--job`, and optional `--output`. |
+
+Examples:
+
+```sh
+agentia testing test create --project <project-id> --robot <robot-id> --name "Smoke" --file tests/smoke.robot --json
+agentia testing test run <job-id> --project <project-id> --wait-for-result --json
+agentia testing test logs <build-id> --project <project-id> --job <job-id> --output ./crt.log --json
+```
+
+## Related CRT Commands
+
+| Area | Commands | Use For |
+| --- | --- | --- |
+| Projects | `testing project list/create/get/delete` | Top-level CRT project lifecycle. |
+| Robots | `testing robot list/create/get/delete` | Robot worker definitions. |
+| Jobs | `testing job list/create/get/update/delete/files/upload/download` | CRT job/test definitions and file storage. |
+| Builds | `testing build run/list/logs/abort` | Lower-level run/build management. |
+| Variables | `testing variable list/create/update/delete` | CRT variables, with value redaction in output. |
+
+Use related commands to discover IDs needed by `testing test`.
+
+## Git-Backed Tests
+
+Some CRT tests store Robot files in Git. Use Git-backed flags only when the project already expects Git storage or the user asks for it. Preserve branch, path, and credential values from existing job details when updating.
+
+## Gotchas
+
+- The `testing test` namespace and the shorter `testing` namespace overlap. Prefer `testing test` in generated guidance because it makes the CRT domain explicit.
+- There is no `testing test get` or `testing test delete`; use `testing job get` or `testing job delete` for CRT job/test definitions.
+- `testing test run --wait-for-result` can poll until a terminal build status. Without it, the command may return only the started build.
+- Log commands may write files. In JSON mode, keep stdout structured and report the output path instead of mixing log text with JSON.