Run your coding agent off GitHub issues instead of chat prompts

Leon van Zyl logs and labels GitHub issues with dependencies for every piece of work, then tells Claude Code to read the outstanding issues and implement them one by one.

Leon van Zyl · YouTube · published Oct 29, 2026 · Software & DevOps

Run your coding agent off GitHub issues instead of chat prompts — video by Leon van Zyl▶ Watch on YouTube
Prompt
Read all the outstanding issues on my GitHub repository [repo name] and implement them one by one, respecting the labels and dependencies between them.

Visual breakdown

Leon keeps a GitHub repository for every project and logs each piece of work as a GitHub issue, written by him or by the agent. Claude Code is then told to read the outstanding issues and implement them one by one.

The problem: Work requested in chat is hard to track. You want one place that shows the status of all your work and that the agent can pick up from.

From issue to implemented work

  1. GitHub repositorySet up for every new or existing project
  2. Log an issueYou write it yourself, or ask your agent to create it
  3. Label and linkAdd labels and set dependencies between issues
  4. Claude CodeReads all outstanding issues on the project
  5. Implement one by oneWorks through the issues in order
  6. Finished workStatus of all work is visible in the issue list
Source of truthManual setupAI agentResult

What makes issues useful

  1. Issues can be labeled
  2. Dependencies can be set between them
  3. They show the status of all your work

By the numbers

Try it on your own project

Start with a GitHub repository, then route every request through issues instead of one-off chat prompts.

  1. Make sure the project has a GitHub repository
  2. Log a GitHub issue for the next piece of work, or have your agent create it
  3. Label the issues and set dependencies between them
  4. Open Claude Code and ask it to read all outstanding issues
  5. Tell it to implement them one by one

Leon says this builds toward a world where you, or even your users, only log a bug or issue and coding agents run in the background.

Takeaways from the clip

  • Do this for new projects and existing ones alike.
  • The agent can write the issues for you, so logging them costs almost nothing.
  • Labels and dependencies keep the order of work clear.
  • The goal is that you don't have to interact with Claude Code yourself for every task.

Distilled from the video’s captions

How to try it

  1. Open Claude Code.
  2. Copy the prompt and fill in the [placeholders].
  3. Watch Leon van Zyl's video for the full walkthrough and setup.

Related use cases

Share