action-remediate
Remediate GitHub Actions action findings identified by the action-audit skill. Applies the appropriate fix per action type — @main ref for internal bitwarden/ actions, full SHA with inline version comment for external actions, or full replacement — across selected repos and creates draft PRs. Run the action-audit skill first to identify findings before using this skill. User: Go ahead and fix the unpinned actions from the audit Action: Trigger action-remediate to apply fixes and create PRs User: Replace tj-actions/changed-files with the safe version across those repos Action: Trigger action-remediate to swap the action and create PRs
- Installs
- 64
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/bitwarden/ai-plugins --skill action-remediate- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads action-remediate automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Rules
- No mutating API calls without confirmation.
gh apiGET requests are allowed freely. Any call using-X POST,-X PUT,-X PATCH, or-X DELETEmust 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 handing off for 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
- pin to main — for internal
- The target SHA, replacement action, or confirmation that
@mainis the fix
If any of this is unclear, ask the user before continuing.
Step 2: Apply Fixes Per Repo
For each selected repo:
-
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. -
Create a fix branch:
git checkout -b fix/action-remediation-<action-name-slug> -
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 withuses: <action>@<sha> # <original-ref> - Replace: Before applying, verify the replacement action is on Bitwarden's approved actions list in
bitwarden/workflow-linter. Then swapuses: <old-action>@<ref>withuses: <new-action>@<sha> # <tag>
- Pin to main (internal
-
Show a
git diffof changes in this repo and get confirmation before proceeding.
Step 3: Commit, Push, and Create PRs
Do not run the staging, commit, or push commands yourself. For each repo, present the block below for the user to run manually as a suggestion:
git add .github/
git commit -m "Remediate <action-name> action usage"
git push -u origin fix/action-remediation-<action-name-slug>
Once the user confirms the push, create the draft PR:
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:
| Repo | Files Changed | PR Created | Notes |
|---|---|---|---|
| ... | ... | ... | ... |
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.
FAQ
What does the action-remediate skill do?
Remediate GitHub Actions action findings identified by the action-audit skill. Applies the appropriate fix per action type — @main ref for internal bitwarden/ actions, full SHA with inline version comment for external actions, or full replacement — across selected repos and creates draft PRs. Run the action-audit skill first to identify findings before using this skill. User: Go ahead and fix the unpinned actions from the audit Action: Trigger action-remediate to apply fixes and create PRs User: Replace tj-actions/changed-files with the safe version across those repos Action: Trigger action-remediate to swap the action and create PRs
How do I install action-remediate?
Run npx skills add https://github.com/bitwarden/ai-plugins --skill action-remediate in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/action-remediate/ (personal) or .claude/skills/action-remediate/ (project).
Which AI agents can use action-remediate?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is action-remediate safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains action-remediate?
It is published by bitwarden in bitwarden/ai-plugins, and it is an official skill from the maker of the technology it covers. It has 64 recorded installs.
More from bitwarden/ai-plugins
reviewing-security-architecture
bitwarden/ai-plugins
Open the skill to read its SKILL.md instructions.
threat-modeling
bitwarden/ai-plugins
Open the skill to read its SKILL.md instructions.
retrospecting
bitwarden/ai-plugins
Open the skill to read its SKILL.md instructions.
avoiding-false-positives
bitwarden/ai-plugins
Use this skill to validate findings during a code review. For each finding, run the rejection criteria and verification checks. If a finding fails any check, drop it. In PR mode it also holds the once-per-review stacked-PR gate that decides whether completeness findings apply to the pull request at all.
reviewing-claude-config
bitwarden/ai-plugins
Open the skill to read its SKILL.md instructions.
posting-review-summary
bitwarden/ai-plugins
Open the skill to read its SKILL.md instructions.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.