Codez Use Case Workflow
Lately, I’ve been obsessed with Agentic Coding and built a small project called Codez, which runs the Codex CLI directly inside GitHub Actions. It’s been working quite well. Here’s an example of a workflow it supports:
Discuss with AI first → break down the problem → tackle each part one by one
Take this code refactoring request as an example: Issue #304
Step 1: Raise the Requirement
In the issue, I clearly described what I wanted to do, including points to discuss and related background info. The title and content of the issue become part of the initial prompt for the agent.
Then, I triggered the agent directly in the comments:
1 | /codex # Keyword to wake up the agent |
With that, the agent gets to work. Even though it doesn’t have network access during runtime, it can still give some solid initial ideas using the context (codebase, content cached from the provided links, and the issue itself).
Step 2: Automatically Break Down into Actionable Tickets
Next, I triggered the agent again. This time to generate a series of issues:
1 | /codex |
Note: Only flags in the current comment are recognized. The agent then organizes the discussion into multiple issues. Each issue can be worked on independently.
These newly created tickets can now be handled one by one. Like this:
Final Step: Let the Agent Do the Work
The entire workflow feels like genuine team collaboration: discuss first, break down the problem, then work in parallel. The difference is that humans are replaced by agents.
Some say Agentic Coding is like catnip for programmers, totally addictive. It’s true.