@astrofoundry/pi-astro 0.2.12 → 0.3.1

package/skills/postman-cli/references/reporters.md

@@ -0,0 +1,94 @@
+# Reporters and Report Customization
+
+The Postman CLI has built-in reporters to generate collection run reports. Four reporters are available: CLI, JSON, JUnit, and HTML.
+
+**Important:** JSON, JUnit, and HTML reporters only work with v2 format (JSON) collections. v3 format (YAML) collections only support the CLI reporter.
+
+## Available reporters
+
+### CLI (default)
+
+Displays a report in the terminal. Always shown unless `--silent` is used.
+
+```bash
+postman collection run ./collection -r cli
+```
+
+### JSON
+
+Creates a JSON file with full run details including request/response data.
+
+```bash
+postman collection run ./collection -r json
+postman collection run ./collection -r json --reporter-json-export ./reports/result.json
+
+# use Newman-compatible JSON structure
+postman collection run ./collection -r json --reporter-json-structure newman
+```
+
+### JUnit
+
+Creates an XML file compatible with CI/CD tools that consume JUnit format.
+
+```bash
+postman collection run ./collection -r junit
+postman collection run ./collection -r junit --reporter-junit-export ./reports/result.xml
+```
+
+### HTML
+
+Creates an interactive HTML report. You can filter iterations by test failures or errors.
+
+```bash
+postman collection run ./collection -r html
+postman collection run ./collection -r html --reporter-html-export ./reports/result.html
+```
+
+## Multiple reporters
+
+Combine reporters with comma-separated list:
+
+```bash
+postman collection run ./collection -r cli,json,junit,html
+```
+
+## Custom export paths
+
+By default, reports are saved to `./postman-cli-reports/` with filenames like `collection-name-yyyy-mm-dd-hh-mm-ss`. Override with:
+
+```bash
+--reporter-json-export <path>
+--reporter-junit-export <path>
+--reporter-html-export <path>
+```
+
+If the path is an existing directory, the report file is saved inside it. If the directory does not exist, it is created automatically.
+
+## Omitting sensitive data
+
+Remove request/response bodies and headers from reports:
+
+```bash
+# omit request bodies
+--reporter-json-omitRequestBodies
+--reporter-html-omitRequestBodies
+
+# omit response bodies
+--reporter-json-omitResponseBodies
+--reporter-html-omitResponseBodies
+
+# omit all headers
+--reporter-json-omitHeaders
+--reporter-html-omitHeaders
+
+# omit everything (headers + bodies)
+--reporter-json-omitAllHeadersAndBody
+--reporter-html-omitAllHeadersAndBody
+```
+
+## CI/CD usage
+
+```bash
+# generate JUnit report for CI consumption, fail on test errors
+postman collection run ./collection -r junit --reporter-junit-export ./test-results/postman.xml --bail
+```

package/skills/postman-cli/references/request-scripting.md

@@ -0,0 +1,69 @@
+# Request Scripting and Chaining
+
+The `postman request` command supports pre-request and post-response scripts using the Postman scripting sandbox (pm.* API).
+
+## Post-response scripts
+
+Use `--script-post-request` to run JavaScript after receiving the response:
+
+```bash
+# validate response
+postman request https://api.example.com/health \
+  --script-post-request "pm.test('Health check', function() { pm.expect(pm.response.json().status).to.equal('healthy'); });"
+
+# extract and log data
+postman request POST https://api.example.com/login \
+  --body '{"user":"admin","pass":"secret"}' \
+  --script-post-request "const token = pm.response.json().token; console.log('Token:', token);"
+```
+
+## Chaining requests
+
+Use shell command substitution with `--response-only` to chain requests:
+
+```bash
+# get a token, then use it in the next request
+TOKEN=$(postman request POST https://api.example.com/login \
+  --body '{"username":"admin","password":"pass"}' \
+  --response-only | jq -r '.token')
+
+postman request https://api.example.com/protected \
+  --auth-bearer-token "$TOKEN"
+```
+
+## Collection scripts
+
+Collection files (.yaml or .json) can include scripts at the collection, folder, and request levels:
+
+```yaml
+# in a request YAML file
+scripts:
+  - type: afterResponse
+    code: |-
+      pm.test('Status 200', () => pm.response.to.have.status(200));
+      const res = pm.response.json();
+      pm.environment.set('_odoo_order_id', res);
+    language: text/javascript
+```
+
+Script-managed variables (prefixed with `_`) are set during collection runs and chained between requests using `pm.environment.set()` and `{{variable}}` syntax.
+
+## Available pm.* API in scripts
+
+- `pm.response.json()` — parsed JSON response body
+- `pm.response.to.have.status(code)` — assert status code
+- `pm.expect(value)` — Chai BDD assertion
+- `pm.environment.set(key, value)` — set environment variable for subsequent requests
+- `pm.environment.get(key)` — get environment variable
+- `pm.globals.set(key, value)` — set global variable
+- `pm.globals.get(key)` — get global variable
+- `console.log(...)` — log to terminal output
+
+## Exit codes from tests
+
+When scripts contain `pm.test()` assertions, the exit code equals the number of failed tests. This makes it suitable for CI/CD pipelines:
+
+```bash
+postman collection run ./collection --bail --failure
+echo "Exit code: $?"
+```

package/skills/raycast-script-creator/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: raycast-script-creator
+description: Create and install a Raycast script command in /Users/astronaute/.config/raycast/script-commands, then register it with chezmoi after the user confirms it works in Raycast. Trigger whenever the user asks to make, add, build, or scaffold a Raycast script, Raycast command, Raycast shortcut, or any shell/zsh command they want to launch from Raycast — even if they don't use the word "script". Use this for ANY request about automating something through Raycast from the keyboard.
+---
+
+# Raycast Script Creator
+
+Create a Raycast script command in zsh, drop it in the user's script-commands folder, let the user confirm it works in Raycast, then track it with `chezmoi add`.
+
+## Defaults
+
+- **Language**: `zsh` (shebang `#!/usr/bin/env zsh`). Only switch if the user explicitly asks.
+- **Location**: `/Users/astronaute/.config/raycast/script-commands/` (flat, no subfolders).
+- **Filename**: kebab-case of the title + extension matching the language (`.sh` for zsh/bash, `.py` for python, `.applescript` for AppleScript, `.js` for node…).
+- **Author**: `astronaute`.
+- **Icon**: `🤖` unless overridden.
+- **authorURL**: omit.
+
+## Workflow
+
+### 1. Gather intent
+
+From the user prompt, decide:
+- **Behavior** — what the script does.
+- **Title** — human-readable, Apple-Style-Guide-ish (`Toggle Hidden Files`, `Open Today's Journal`).
+- **Mode** — `silent` (fire-and-forget), `compact` (short result line), `fullOutput` (long output window), `inline` (live in root search, needs `refreshTime`).
+- **Arguments** — up to 3 positional args, each with `name`, `placeholder`, optional `optional`/`secure`.
+- **needsConfirmation** — true for destructive commands.
+
+If anything is ambiguous, ask ONE concise question with a recommended default — never ask blind.
+
+### 2. Verify metadata spec via grimoire
+
+Before writing, confirm the current Raycast metadata keys. Do not rely on memory:
+
+    grimoire search "script command metadata headers" --source raycast-script-commands --top 3
+
+Run follow-up searches for edge cases (arguments, icons, refreshTime, packageName).
+
+### 3. Write the script
+
+Use the **Write** tool (MCP file-writing is disallowed in this project).
+
+Template — **follow the exact section structure below**. Raycast's own template (`templates/script-command.template.sh` in `raycast/script-commands`) groups metadata into three commented sections. Missing `packageName` or skipping these section headers has caused scripts not to appear in Raycast root search even when the required keys are all present.
+
+    #!/usr/bin/env zsh
+
+    # Required parameters:
+    # @raycast.schemaVersion 1
+    # @raycast.title <Title>
+    # @raycast.mode <mode>
+    # @raycast.packageName <Package>
+
+    # Optional parameters:
+    # @raycast.icon 🤖
+    # @raycast.argument1 { "type": "text", "placeholder": "..." }
+    # @raycast.currentDirectoryPath ~              # only if needed
+    # @raycast.needsConfirmation true              # only if true
+
+    # Documentation:
+    # @raycast.description <one-sentence description>
+    # @raycast.author astronaute
+
+    set -euo pipefail
+
+    <script body>
+
+Rules:
+- **Always include `@raycast.packageName`** — e.g. `Security`, `System`, `Developer`, `Network`. It's the root-search subtitle and empirically required for the command to be discovered reliably.
+- **Keep the three section header comments** (`# Required parameters:`, `# Optional parameters:`, `# Documentation:`) — they match the official template and the working scripts already in the folder.
+- **Keep the argument `placeholder` simple text**: no parentheses, no quotes, no JSON-breaking characters. `"prefix"` is fine; `"prefix (e.g. foo)"` is risky.
+- `set -euo pipefail` on every zsh/bash script — fail fast aligns with the user's anti-defensive-programming philosophy.
+- Double quotes around every string literal (project Rule 12).
+- No useless comments (project Rule 5).
+- Blank line separating metadata block from script body; Raycast needs a contiguous comment block at the top.
+
+### 4. Make it executable
+
+    chmod +x /Users/astronaute/.config/raycast/script-commands/<filename>
+
+### 5. Ask the user to test
+
+Say exactly:
+
+> Open Raycast, search for **"<Title>"**, run it, and confirm it works as expected. Reply `ok` to track it with chezmoi, or describe the issue.
+
+Wait. Do **not** run `chezmoi add` before the user confirms.
+
+### 6. Track with chezmoi
+
+On confirmation:
+
+    chezmoi add /Users/astronaute/.config/raycast/script-commands/<filename>
+
+Surface any chezmoi error verbatim — no silent retries. Do **not** run `chezmoi apply`.
+
+## Output modes — quick reference
+
+| Mode | Use when |
+|------|----------|
+| `silent` | Side-effect commands (toggle, copy, open). HUD only. |
+| `compact` | Short success/error message or one-liner result. |
+| `fullOutput` | Long / multi-line output (logs, lists). |
+| `inline` | Live result in root search (system info). Requires `refreshTime`. |
+
+## Arguments — quick reference
+
+    # @raycast.argument1 { "type": "text", "placeholder": "name" }
+    # @raycast.argument2 { "type": "dropdown", "placeholder": "env", "data": [{ "title": "Prod", "value": "prod" }] }
+
+Positional inside the script: `$1`, `$2`, `$3`.
+
+## Example
+
+User: *"Create a Raycast script to copy my public IP to the clipboard."*
+
+1. Title `Copy Public IP`, mode `silent`, icon `🌐`, no args.
+2. Confirm any uncertain fields with the user.
+3. `grimoire search "script command metadata headers" --source raycast-script-commands`.
+4. Write `/Users/astronaute/.config/raycast/script-commands/copy-public-ip.sh`.
+5. `chmod +x`.
+6. Ask user to test in Raycast.
+7. On `ok`, `chezmoi add <path>`.
+
+## Avoid
+
+- Writing via MCP tools — use Write.
+- Env-var fallbacks unless user asks (project Rule 9).
+- Disabling shell errors (`set +e`) without confirmation.
+- Running `chezmoi apply` — only `add`.
+- Creating subfolders inside `script-commands/`.
+- Committing or pushing anything — out of scope.

package/themes/astro.json

@@ -0,0 +1,76 @@
+{
+    "$schema": "https://raw.githubusercontent.com/badlogic/pi-mono/main/packages/coding-agent/src/modes/interactive/theme/theme-schema.json",
+    "name": "astro",
+    "vars": {
+        "bg": "#0D1117",
+        "bgLift": "#161B22",
+        "bgSelect": "#1C2128",
+        "border": "#30363D",
+        "accent": "#FFD700",
+        "text": "#E6EDF3",
+        "muted": "#8B949E",
+        "dim": "#6E7681",
+        "success": "#3FB950",
+        "error": "#F85149",
+        "warning": "#DB6D28"
+    },
+    "colors": {
+        "accent": "accent",
+        "border": "border",
+        "borderAccent": "accent",
+        "borderMuted": "#21262D",
+        "success": "success",
+        "error": "error",
+        "warning": "warning",
+        "muted": "muted",
+        "dim": "dim",
+        "text": "text",
+        "thinkingText": "muted",
+
+        "selectedBg": "bgSelect",
+        "userMessageBg": "bgLift",
+        "userMessageText": "text",
+        "customMessageBg": "#1F1D2E",
+        "customMessageText": "#C9D1D9",
+        "customMessageLabel": "accent",
+        "toolPendingBg": "#21262D",
+        "toolSuccessBg": "#0E2818",
+        "toolErrorBg": "#2D0E11",
+        "toolTitle": "accent",
+        "toolOutput": "#C9D1D9",
+
+        "syntaxComment": "muted",
+        "syntaxKeyword": "#FF7B72",
+        "syntaxFunction": "#D2A8FF",
+        "syntaxVariable": "#FFA657",
+        "syntaxString": "#A5D6FF",
+        "syntaxNumber": "#79C0FF",
+        "syntaxType": "#7EE787",
+        "syntaxOperator": "#FF7B72",
+        "syntaxPunctuation": "#C9D1D9",
+
+        "mdHeading": "accent",
+        "mdLink": "#58A6FF",
+        "mdLinkUrl": "dim",
+        "mdCode": "#FF7B72",
+        "mdCodeBlock": "text",
+        "mdCodeBlockBorder": "border",
+        "mdQuote": "muted",
+        "mdQuoteBorder": "#B58900",
+        "mdHr": "border",
+        "mdListBullet": "muted",
+
+        "toolDiffAdded": "success",
+        "toolDiffRemoved": "error",
+        "toolDiffContext": "muted",
+
+        "thinkingOff": "#3D2F0A",
+        "thinkingMinimal": "#5C4713",
+        "thinkingLow": "#8B6914",
+        "thinkingMedium": "#B58900",
+        "thinkingHigh": "#DAA520",
+        "thinkingXhigh": "accent",
+
+        "bashMode": "#39C5CF"
+    }
+}