GitHub Actions Docs

Docs-grounded help for GitHub Actions — the automation that runs when you push code (e.g. auto-test or auto-deploy). It answers from the official GitHub docs instead of stale memory, so the YAML it gives you is current. Relevant if we put a connector repo on GitHub with auto-deploy.

Cowork & Chat

How to use it

Ask how to write, fix, secure, or migrate a workflow and Claude finds the authoritative GitHub doc page and gives docs-backed YAML and the exact link. Works in Cowork/Chat — it’s research + guidance you can copy; it doesn’t run the pipeline for you.

How to invoke / keep it on

Ask a GitHub Actions question (syntax, secrets, deploys, migration) and Claude loads it automatically.

20 powerful examples for Melinda Maria

Copy, tweak, make them yours. Just describe the task — Claude loads the skill automatically.

01"Write a GitHub Actions workflow that auto-deploys a connector to Cloudflare with wrangler whenever I push to main, and link the official docs for each part."

02"Explain in plain English how to store our Cloudflare API token as a GitHub secret so it’s never in the code."

03"Set up a workflow that runs our tests on every pull request before anything can merge."

04"I’m moving a project from another CI system to GitHub Actions — show me the equivalent workflow, grounded in the docs."

05"Write a workflow that deploys the onboarding hub to Cloudflare Pages on every push to main, with the docs links."

06"Set up the planned mm-knowledge-docs repo so a push triggers a sync, and show me the trigger syntax from the docs."

07"Explain how to run a job only when files in a specific folder change, so a connector deploy only fires for that connector."

08"Help me add a manual “deploy” button (workflow_dispatch) so I can trigger a release on demand."

09"Show me how to require a passing check before a pull request can be merged, per GitHub’s branch-protection docs."

10"Write a workflow that lints and type-checks a TypeScript connector on every PR."

11"Explain how secrets are scoped (repo vs environment) so production credentials aren’t exposed to forks."

12"Set up a scheduled workflow that runs a connector health check every morning and reports failures."

13"Help me cache dependencies in a workflow so deploys run faster, with the current caching syntax."

14"Show me how to use environments with required reviewers so a production deploy needs a human approval."

15"Write a matrix workflow that tests across two Node versions, grounded in the docs."

16"Explain how to pass an output from one job to another safely."

17"Help me debug a failing workflow — what does this error mean and where do the docs say to fix it?"

18"Set up a workflow that posts a Slack message to #mm-claude when a deploy succeeds or fails."

19"Show me how to pin third-party actions to a safe version to avoid supply-chain risk, per GitHub guidance."

20"Draft a plain-English explainer for the team on what “CI/CD” means and what our workflows actually do."

← Back to Engineering & Prompt-craft