linux-test
Run integration tests that require Linux (full loopback range 127.x.x.x) via Docker. Use when a test fails on macOS with "Can't assign requested address" or when the user says "/linux-test".
What this skill does
# Linux Integration Test Runner ## Overview Some Freenet integration tests require Linux's full loopback range (`127.x.x.x`) and fail on macOS with "Can't assign requested address". This skill runs those tests inside a Docker container using the `docker/test-runner/` infrastructure. ## Arguments - **Test name only:** `/freenet:linux-test run_delegate_messaging_e2e` — auto-wraps as `cargo test` with `--nocapture` - **Full cargo args:** `/freenet:linux-test cargo test -p freenet -- test_name` — passed through directly - **No args:** Show usage help and list known Linux-required tests ## Known Linux-Required Tests These tests bind multiple loopback addresses and need Linux: | Test | Package | |------|---------| | `run_app_blocked_peers` | `freenet-ping-app` | | `run_delegate_messaging_e2e` | `freenet-ping-app` | | `run_app_delegate_wasmtime` | `freenet-ping-app` | | `edge_case_state_sizes` | `freenet` | | `error_notification` | `freenet` | | Tests in `connectivity.rs` | `freenet` | ## Step 1: Parse Arguments Determine the command to run inside Docker: - **No arguments provided:** Display the usage help below and stop. ``` Usage: /freenet:linux-test <test_name_or_cargo_args> Examples: /freenet:linux-test run_delegate_messaging_e2e /freenet:linux-test cargo test -p freenet -- test_name /freenet:linux-test cargo test -p freenet-ping-app --test run_app_blocked_peers -- --nocapture Known Linux-required tests: - run_app_blocked_peers (freenet-ping-app) - run_delegate_messaging_e2e (freenet-ping-app) - run_app_delegate_wasmtime (freenet-ping-app) - edge_case_state_sizes (freenet) - error_notification (freenet) - connectivity tests (freenet) ``` - **Starts with `cargo`:** Use arguments as-is. Append `-- --nocapture` if no `--` separator is present. - **Just a test name:** Map to the appropriate cargo test command: - If the test name matches a known test above, use the correct package. - Otherwise, default to: `cargo test -p freenet --test <name> -- --nocapture` - For `freenet-ping-app` tests: `cargo test -p freenet-ping-app --test <name> -- --nocapture` ## Step 2: Ensure Docker Image Exists ```bash # Check if the image exists docker image inspect freenet-test-runner >/dev/null 2>&1 ``` If the image does NOT exist, build it: ```bash docker build -t freenet-test-runner -f docker/test-runner/Dockerfile . ``` Tell the user: "Building Docker image `freenet-test-runner` (first time only, takes a few minutes)..." ## Step 3: Run the Test Execute the test using `docker/test-runner/run.sh`: ```bash docker/test-runner/run.sh <command args> ``` **Important:** Use `run_in_background` for the Bash tool since tests can take several minutes. Set a generous timeout (600000ms / 10 minutes). ## Step 4: Report Results After the test completes: - **If exit code is 0:** Report success with a summary of the output (test count, time taken). - **If exit code is non-zero:** Report failure. Show the relevant error output (last ~50 lines). Look for panic messages, assertion failures, or compilation errors and highlight them. ## Notes - The first run after building the image will compile from scratch (~10-15 min). Subsequent runs use cached builds via Docker volumes. - To reset cached builds: `docker volume rm freenet-test-build freenet-test-target freenet-test-cargo` - Source is mounted read-only; the container rsyncs to a build volume for native Linux filesystem speed.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.