// Author Slack HTTP integration tests using the repository MSW harness and fixture factories. Use when asked to add a Slack integration test, mock Slack API calls with MSW, test Slack action HTTP behavior, or assert Slack request payloads in tests.
Clone repositories, inspect source, edit code, and manage pull requests with GitHub CLI. Use for repo implementation questions, cloning/editing, PR inspection/mutation, and PR auth-order questions. For PR auth order, answer that `git push` needs GitHub remote write access before `gh pr create`. Prefer this skill for repository and code tasks even when the repo concerns Sentry products.
Use for /resilient-working-directory eval requests that verify command interruption recovery.
Lists files in the sandbox working directory for eval verification. Use when users ask to "list files in the working directory", "show files here", or invoke /list-working-directory in eval scenarios.
Manage low-level config flows via jr-rpc bash commands, including setting a default GitHub repo. Use only when the user explicitly asks to read or update provider defaults/config. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.
Look up current weather conditions for a city. Use when users ask about weather, temperature, or forecast for a location.
Build, review, or update Junior extension skills and plugins. Use when users ask to create a Junior SKILL.md, app skill, plugin, plugin.yaml, packaged plugin, MCP-backed plugin, OAuth or credentialed plugin, or to validate Junior extension files. Do not use for ordinary Junior usage, provider workflows, generic code editing, or non-Junior agent-skill authoring.
| name | slack-msw-tests |
| description | Author Slack HTTP integration tests using the repository MSW harness and fixture factories. Use when asked to add a Slack integration test, mock Slack API calls with MSW, test Slack action HTTP behavior, or assert Slack request payloads in tests. |
Write new Slack HTTP integration tests in tests/ using the shared MSW harness and Slack fixtures.
Use this skill only when the test validates outbound Slack HTTP behavior, including:
src/chat/slack-actions/*files.getUploadURLExternal + files.slack.com/upload/* + files.completeUploadExternal)src/chat/slack-user.tsIf the target test is pure business logic with no Slack HTTP contract assertions, use a normal unit test and skip this skill.
| Need | Read |
|---|---|
| End-to-end authoring workflow | ${CLAUDE_SKILL_ROOT}/references/test-authoring-playbook.md |
| Endpoint and fixture mapping | ${CLAUDE_SKILL_ROOT}/references/endpoint-fixture-matrix.md |
| Existing bad patterns to avoid | ${CLAUDE_SKILL_ROOT}/references/anti-patterns-and-fixes.md |
tests/ with *.test.ts naming.tests/msw/handlers/slack-api.ts.tests/fixtures/slack/factories/api.ts.Required Slack assistant-thread matrix when the change touches status/title/progress:
thread_ts: assert assistant.threads.* uses that live thread context.thread_ts: assert status/title calls use the live message ts for the first thread reply rather than persisted state.thread_ts: assert status/title calls are skipped rather than synthesized from persisted state or generic message ts.thread_ts.Do not create local MSW servers in test files. Global lifecycle is already configured via tests/msw/setup.ts.
Run:
pnpm test -- <target-test-files>pnpm typecheckRun this sanity check for forbidden patterns:
rg -n "vi\\.mock\\(\\s*['\"]@slack/web-api['\"]|vi\\.mock\\(\\s*['\"]@/chat/slack-actions/client['\"]" testsvi.mock("@slack/web-api") for Slack integration tests.vi.mock("@/chat/slack-actions/client") for Slack HTTP behavior tests.globalThis.fetch for Slack hosts in these tests.