Action Remediate

Rules

• No mutating API calls without confirmation. gh api GET requests are allowed freely. Any call using -X POST, -X PUT, -X PATCH, or -X DELETE must be shown to the user and approved before execution.
• Never force-push, delete branches, or delete repositories.
• Only modify files under `.github/`. Do not touch application code, scripts, or configuration outside of workflow files.
• Show a diff and get confirmation before every commit.
• All PRs must be created as drafts.
• Flag uncertainty. If a finding is ambiguous or a fix could break a workflow, stop and ask rather than guessing.

Step 1: Confirm Audit Findings

Before proceeding, verify that the user has audit findings to act on. These should come from a prior run of the action-audit skill. Confirm:

• Which repos to remediate (all, a subset, or specific ones)
• The remediation approach:
• pin to main — for internal bitwarden/ actions: change the ref to @main
• pin update — for external actions: update to a verified 40-character SHA with an inline version comment
• replace — swap to a different action entirely
• The target SHA, replacement action, or confirmation that @main is the fix

If any of this is unclear, ask the user before continuing.

Step 2: Apply Fixes Per Repo

For each selected repo:

1. Ask the user for the base directory where their repos are cloned (if not already known). Check if a local clone exists at <base-dir>/<repo>. If not, inform the user and skip that repo.

2. Create a fix branch:

   git checkout -b fix/action-remediation-<action-name-slug>

3. Apply the fix to each affected file based on the remediation approach:

• Pin to main (internal `bitwarden/` actions): Replace the ref with @main — e.g., uses: bitwarden/gh-actions/action@v1 → uses: bitwarden/gh-actions/action@main. No SHA resolution needed.
• Pin update (external actions): Replace the uses: line with uses: <action>@<sha> # <original-ref>
• Replace: Before applying, verify the replacement action is on Bitwarden's approved actions list in bitwarden/workflow-linter. Then swap uses: <old-action>@<ref> with uses: <new-action>@<sha> # <tag>

4. Show a git diff of changes in this repo and get confirmation before proceeding.

Step 3: Create PRs

After fixes are confirmed, for each repo:

git add .github/
git commit -m "Remediate <action-name> action usage"
gh pr create \
  --title "Remediate <action-name> action usage" \
  --body "$(cat <<'EOF'
## Summary

Remediates usage of `<action-name>` across this repository.

**Action taken:** <pin updated to `<sha>` / replaced with `<new-action>`>

**Reason:** <compromised action / deprecated action / unpinned reference>
EOF
)" \
  --draft

Step 4: Final Summary

Output a summary of all actions taken:

Remind the user that code search results may have a lag and to verify no repos were missed by checking manually if this is a security incident.