gh-awScheduleNot executed· 1 caveat

Daily repo status report issue

Runs daily. The agent writes a status report on recent repository activity (issues, pull requests and progress) and posts it as an issue.

schedule: daily + workflow_dispatch

Copy agent prompt Get the YAML Source ↗

How it works

From event to result

Trigger: GitHub starts a run when the schedule in this block is due, or you run it by hand.
Agent: GitHub Agentic Workflows (gh-aw), using the the engine in this block engine. You compile this file; gh-aw does not run the markdown as-is.
What it does: Runs daily. The agent writes a status report on recent repository activity (issues, pull requests and progress) and posts it as an issue.
What you get: This listing does not state a pull request or a comment. Read the prompt, and treat the result as not executed.

Setup

Where to paste this

Create .github/workflows/agentics-daily-repo-status.md (markdown, not a .yml file).
Paste the source below into that file, then run gh aw compile. Actions runs the compiled file at .github/workflows/agentics-daily-repo-status.lock.yml.
This file does not name a repository secret. If the engine needs a credential, the name is not written here. Check that engine’s docs before you add one.

Let your agent do it

Copy a prompt for Claude Code, Codex, or Cursor.

Paste it into your coding agent in this repo. It does the setup and asks before anything leaves your machine.

Runs the same job in your agent session, on the plan you are signed in with. No API key, no Action.

Do the job of the "Daily repo status report issue" workflow from AgentFlows (https://agentflows.sh/flows/agentics-daily-repo-status) right here, in this session, using the plan I'm signed in with. No API key and no GitHub Action.

What it does: Runs daily. The agent writes a status report on recent repository activity (issues, pull requests and progress) and posts it as an issue.

The workflow normally runs on: schedule: daily + workflow_dispatch. Instead, ask me which pull request, issue, or branch to work on, then follow these instructions:

```text
# Repo Status

Create an upbeat daily status report for the repo as a GitHub issue.

## What to include

- Recent repository activity (issues, PRs, discussions, releases, code changes)
- Progress tracking, goal reminders and highlights
- Project status and recommendations
- Actionable next steps for maintainers

## Style

- Be positive, encouraging, and helpful 🌟
- Use emojis moderately for engagement
- Keep it concise - adjust length based on actual activity

## Process

1. Gather recent activity from the repository
2. Study the repository, its issues and its pull requests
3. Create a new GitHub issue with your findings and insights
```

Use the gh CLI for anything on GitHub, and show me what you plan to post or change before you do it.

The file

Workflow YAML

Copy the file as-is. The notes beside each block explain it.

.github/workflows/agentics-daily-repo-status.md

File

gh-aw source. Paste it as markdown, then compile. It is not a finished Actions YAML file.

1---2description: |3  This workflow creates daily repo status reports. It gathers recent repository4  activity (issues, PRs, discussions, releases, code changes) and generates5  engaging GitHub issues with productivity insights, community highlights,6  and project recommendations.7

Trigger

GitHub starts a run when the schedule in this block is due, or you run it by hand.

8on:9  schedule: daily10  workflow_dispatch:11

Permissions

This token may read the repo, read issues, read pull requests, network: defaults, and lockdown: false. Anything not listed is not granted.

12permissions:13  contents: read14  issues: read15  pull-requests: read1617network: defaults1819tools:20  bash: ["cat", "ls", "find", "grep", "head", "tail", "wc"]21  github:22    # If in a public repo, setting `lockdown: false` allows23    # reading issues, pull requests and comments from 3rd-parties24    # If in a private repo this has no particular effect.25    lockdown: false26    min-integrity: none # This workflow is allowed to examine and comment on any issues27

What you get

What the agent is allowed to write back: mentions, allowed-github-references, create-issue. gh-aw blocks other writes.

28safe-outputs:29  mentions: false30  allowed-github-references: []31  create-issue:32    title-prefix: "[repo-status] "33    labels: [report, daily-status]34    close-older-issues: true35---3637# Repo Status3839Create an upbeat daily status report for the repo as a GitHub issue.4041## What to include4243- Recent repository activity (issues, PRs, discussions, releases, code changes)44- Progress tracking, goal reminders and highlights45- Project status and recommendations46- Actionable next steps for maintainers4748## Style4950- Be positive, encouraging, and helpful 🌟51- Use emojis moderately for engagement52- Keep it concise - adjust length based on actual activity5354## Process55561. Gather recent activity from the repository572. Study the repository, its issues and its pull requests583. Create a new GitHub issue with your findings and insights

Keep going

More workflows

All workflows

gh-awIssue opened
17
gh-aw: agentic issue triage with safe label output
gh-aw source is Markdown + YAML frontmatter compiled with `gh aw compile` to a .lock.yml. Writes go through `safe-outputs`.
issues: opened
Est. cost per run~$0.02 runner + engine tokens/credits (UNVERIFIED)Checked Oct 16, 2026
Not executed· 2 caveats
gh-awLabel
18
gh-aw: run an AI review when `ai-review` label is added
`label_command` removes the label after activation by default (`remove_label: true`).
label_command: ai-review
Est. cost per run~$0.03 runner + engine tokens/credits (UNVERIFIED)Checked Oct 16, 2026
Not executed· 1 caveat
gh-awSchedule
19
gh-aw: daily CI optimization coach (GitHub's own)
Trimmed from gh-aw's own .github/workflows/ci-coach.md (removed imports, experiments, AI-credit caps).
schedule: daily + workflow_dispatch
Est. cost per run~$0.12 runner + engine tokens/credits (UNVERIFIED)Checked Oct 16, 2026
Not executed· 1 caveat