Hire an AI GitHub Actions workflow reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• Build cost review
• Security findings
• Proposed runtime changes and validation

How it does the job well

• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.
• Treat input from users, files and networks as untrusted. Validate it at the boundary.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: Your GitHub Actions bill or build minutes keep rising.

• Build cost review. Where build minutes are wasted, and the top fixes ranked by minutes saved.
• Security findings. Risky permissions, unsafe inputs and loose action versions, each with a fix.
• Proposed runtime changes and validation. Supported action versions to move to, and how to check the build still behaves the same.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• GitHub build cost reviewer. Share your Actions workflows. Get wasted build minutes, slow jobs and ways to cut repeat work.
• GitHub Actions permission reviewer. Share your build workflows. Get risky permissions, unsafe inputs and dependency trust problems with fixes.
• GitHub Actions runtime upgrade helper. Share your Actions workflows. Get supported action versions while keeping the build's behavior intact.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id cut-ci-cost-without-weakening-checks only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/cut-ci-cost-without-weakening-checks/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• All your workflow files from .github/workflows/ (attached or pasted)
• Your goal, such as fewer build minutes or faster pull request checks
• Recent run history from gh run list (optional, so savings are measured, not estimated)

Functions and deliverables

• GitHub Actions workflow reviewer: Review wasted build work, risky permissions and outdated action runtimes. Get proposed changes that keep the required checks intact.
  • Build cost review
  • Security findings
  • Proposed runtime changes and validation
• GitHub build cost reviewer: Find wasted build minutes in your GitHub Actions workflows. Get the top 3 fixes to cut repeat work, slow jobs and CI cost.
  • A list of the top causes of wasted minutes and slow builds
  • Up to 3 fixes, ranked by estimated minutes saved per day
  • A note on what was tested live and what was not
  • Expected savings, split into wait time and total runner time
  Source: GitHub Copilot community.
• GitHub Actions permission reviewer: Check your GitHub Actions workflow files for risky permissions, unsafe inputs and unpinned actions. Get each problem with a before and after fix.
  • A table of findings by severity, shown first
  • Each finding with the file, the exact line and the risk in plain words
  • Script injection and risky trigger findings
  • Missing or broad token permissions, and actions not pinned to a full commit
  • A corrected snippet for every critical and high finding
  Source: GitHub Copilot community.
• GitHub Actions runtime updater: Fix GitHub Actions runtime deprecation warnings. Give it your workflow files and get safe, pinned action versions that keep your build working.
  • A list of actions to upgrade, from version and to version
  • A full commit SHA to pin for each action
  • Updated workflow steps that keep your triggers and permissions
  • A note on any action that cannot move to a new major version
  • A checklist to confirm the build still works
  • Notes you can paste into your pull request
  Source: GitHub Copilot community.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• Your GitHub Actions bill or build minutes keep rising.
• You want faster builds without dropping a test, a permission check or a pinned action.

Limits to check before starting

• Your build is failing right now: use the GitHub check failure fixer or the GitHub Actions failure diagnoser.
• You only want a security check of your workflows: use the GitHub Actions permission reviewer.
• You do not use GitHub Actions. These steps read GitHub workflow files only.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the complete skill pack to your AI.
• Share your goal and the files listed above.
• Ask it to follow the steps and mark any missing facts.
• Review the result before approving external actions.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/cut-ci-cost-without-weakening-checks for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.