---
name: al-360-write-your-repo-s-chores-as-plain-english-markdown-and-le
description: "Issue triage, figuring out why CI failed and keeping docs current eat time on every repository. On Oct 28, 2026 GitHub made GitHub Agentic Workflows generally available on Free, Team and Enterprise: you describe the automation in a natural-language Markdown file, it compiles into standard GitHub Actions YAML, and GitHub Copilot or your own coding agent does the work. Agents run with read-only permissions by default inside a sandboxed container, outputs go through a 'safe outputs' check and a threat detection job scans proposed changes before they apply; `gh aw forecast` estimates AI credit spend. An Accenture manager quoted by GitHub says one lead saved an estimated 29 hours a week. The prompt below drafts your first workflow file to start from. Use when the user wants help with repository automation (coding) for a small business."
---

# Write your repo's chores as plain-English Markdown and let a coding agent run them inside GitHub Actions: issue triage, CI failure analysis and docs updates, read-only by default

Issue triage, figuring out why CI failed and keeping docs current eat time on every repository. On Oct 28, 2026 GitHub made GitHub Agentic Workflows generally available on Free, Team and Enterprise: you describe the automation in a natural-language Markdown file, it compiles into standard GitHub Actions YAML, and GitHub Copilot or your own coding agent does the work. Agents run with read-only permissions by default inside a sandboxed container, outputs go through a 'safe outputs' check and a threat detection job scans proposed changes before they apply; `gh aw forecast` estimates AI credit spend. An Accenture manager quoted by GitHub says one lead saved an estimated 29 hours a week. The prompt below drafts your first workflow file to start from.

## Inputs to collect first
Ask the user for anything below that they haven't already given you. Don't guess missing facts.

- What it is, language, how tests and CI run
- Pick one: triage new issues / explain why a CI run failed / update…
- Labels we use, who owns what, what a good issue looks like, files…

## Instructions

Do the task below with the user's inputs in place of each [bracket].

Help me write my first GitHub Agentic Workflow in plain-English Markdown. My repository: [what it is, language, how tests and CI run]. The chore I want automated: [pick one: triage new issues / explain why a CI run failed / update docs when code changes / write missing tests]. Our rules: [labels we use, who owns what, what a good issue looks like, files that must never change]. 1) Write the workflow as a Markdown file: when it runs (the trigger), what the agent should read, the exact steps it should follow, and the only outputs it's allowed to produce (e.g. add labels and one comment, or open a draft pull request), keeping it read-only otherwise. 2) Add instructions for unclear cases: when to ask a human instead of acting. 3) Write 5 test cases (sample issues or failed runs) and what the right result would be for each, so I can check it before turning it on for everyone. 4) Tell me what to check in the compiled Actions YAML and how to use `gh aw forecast` to estimate cost before I enable it. Don't invent commands or settings you aren't sure exist; mark them so I can look them up in the GitHub Agentic Workflows docs.

## Safety checks (share these with the user)

- Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes.
- Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details.
- Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed.

## About this skill

- Works with: GitHub Agentic Workflows (gh aw), GitHub Actions, GitHub Copilot, Claude Code
- Based on this real-world example: https://github.blog/changelog/2026-10-28-github-agentic-workflows-generally-available/
- Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-360-write-your-repo-s-chores-as-plain-english-markdown-and-let-a/
- To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/