Menu
Composes and posts a pipeline bypass request to the
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Deeply gather context from an Azure DevOps work item by following its relations, linked PRs, hyperlinks, and comments. Use whenever a command needs the full picture behind a work item -- planning features, reviewing PRs, triaging, or estimating.
Common steps for creating a new Azure DevOps work item in the FundGuard project, including iteration assignment, parent linking, and triage. Called by create-task, create-bug, and request-environment-access skills — not invoked directly by the user.
Mechanical estimate-and-transition of an Azure DevOps work item to the Triaged state. Called programmatically by skills that create or triage work items -- not invoked directly by the user. For user-initiated triage, use the triage skill instead.
Transitions an Azure DevOps work item to the Active state. Use when starting work on a work item, given an explicit ID or one inferred from the current feature branch.
Marks an Azure DevOps work item as Blocked and links it to its predecessor blocker. Use when a work item cannot proceed until another work item is completed.
Investigates bugs to find root cause, designs a TDD-based fix plan, and implements after approval. Use when given a bug ticket or description of defective behaviour that needs investigation and fixing in the codebase.
| name | submit-bypass-request |
| description | Composes and posts a pipeline bypass request to the |
| disable-model-invocation | true |
Given a PR and a failed pipeline build, compose and post a bypass request to the #pipeline-gated Slack channel (C03R4T6L6J2).
The channel uses a Slack Workflow Builder form ("Submit a Bypass Request") that posts a structured message. Since the workflow form can't be triggered programmatically, this command posts a message in the identical format.
| Input | Description |
|---|---|
| prUrl | (optional) Azure DevOps pull request URL. Resolved automatically from the current branch if omitted. |
| buildId | (optional) Azure DevOps build ID for the failed pipeline. Resolved from the PR's latest build if omitted. |
| stabilityOwner | (optional) Name or Slack handle of the stability owner to ping. |
This command is often invoked after triage-build in the same conversation. When prior triage context is available (build ID, pipeline URL, test failures, commit summary), reuse it -- don't re-fetch from APIs. Steps below note where conversation context can substitute for a fresh lookup.
Determine the PR using one of the following, in priority order:
git branch --show-current).If neither yields a PR, ask the user and stop.
Determine the build using one of the following, in priority order:
If the build succeeded, warn the user that there's nothing to bypass and confirm they want to proceed.
Collect the information needed for the bypass request fields:
_git (with underscore): https://dev.azure.com/<org>/<project>/_git/<repo>/pullrequest/<id>._build (with underscore): https://dev.azure.com/<org>/<project>/_build/results?buildId=<id>&view=results.git merge-base HEAD origin/latest-stable and git merge-base HEAD origin/develop.latest-stable --> "Latest-stable :100:"develop --> "Develop :face_palm:"git log --oneline <target>..HEAD).FE: <@USER_ID> among other area entries. Resolve in priority order:
slack_list_channels (the channel is in SLACK_CHANNEL_IDS), find C03R4T6L6J2, and extract the user ID from the FE: line in the topic field.FE: entry.Format the message in Slack mrkdwn, matching the structure the workflow bot posts.
The external-communications skill governs all of these, but they're critical for this channel -- reinforce them here:
`). Examples: `DtoForge`, `BrowseRepository.ts`, `all-change-requests.spec.ts`.<https://app.currents.dev/instance/abc123|all-change-requests.spec.ts>), Azure DevOps PRs, pipeline builds, and Slack messages (using permalink format). If referencing a previous bypass request, link to the Slack message.The template below is verbatim -- field labels must be wrapped in * for bold rendering in Slack:
Submitted by: <@SLACK_USER_ID>
*PR Link:*
<PR_URL>
*Pipeline link*
<PIPELINE_URL>
*Which branch am I rebased on?*
<BRANCH>
*Roughly, what did I change in the PR?*
<CHANGES_SUMMARY>
*What tests failed, and why do I think it isn't due to my changes?*
<TEST_FAILURE_EXPLANATION>
*Ping the relevant stability owner*
<@STABILITY_OWNER_SLACK_ID>
The "Submitted by" field should be the current user. Look up the user's Slack ID by matching their name or email (from git config user.email) via slack_get_users.
Read and apply the external-communications skill before composing the text below. Follow the objective-communication skill for the free-text fields (changes summary and test-failure explanation). Present the composed message to the user for approval before posting. The user may want to edit the test-failure explanation or change details.
Present the draft as the raw Slack mrkdwn in a fenced code block (copy-pastable, with a copy button).
Post the approved message to channel C03R4T6L6J2 using slack_post_message.
Present a confirmation with a permalink to the posted message (https://fundguard.slack.com/archives/C03R4T6L6J2/p<ts_without_dot>).
Follow the continuous-improvement skill.