githubnext / githubnext/gh-aw-cao
[aw] PR Sous Chef failed
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Workflow Failure
**Workflow:** [PR Sous Chef](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/pr-sous-chef.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/34383322139
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/gh-aw-cao/actions/runs/34383322139
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow pr-sous-chef failure in https://github.com/githubnext/gh-aw-cao/actions/runs/34383322139`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [PR Sous Chef](https://github.com/githubnext/gh-aw-cao/actions/runs/34383322139) · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+pr-sous-chef%22&type=issues)
> - [x] expires on Sep 16, 2026, 5:34 PM UTC
Contributor guide
Research direction
Start with .github/workflows/pr-sous-chef.md and inspect the failed run at https://github.com/githubnext/gh-aw-cao/actions/runs/34383322139. Read .github/skills/agentic-workflows/SKILL.md or the linked debug.md, then identify the workflow failure and confirm the fix by rerunning the workflow successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100