Author: McSomething

and tomorrow is here and I can’t be bothered. It all seems fine so I’m just going to roll through the rest of the issues…

uh-oh…

fixed!

All done…

Let’s just quickly do the last 2 issues…

Issue #10 implemented…

but code review has found some problems…

Fixed some of them. Not sure why it ignored some of them.

Onto the final (#11) issue…

Done and waiting for testing…

Issues…

Fixed…

All done…

/code-review should be run in a clean session after the implementation of an issue because using the same session can include confirmation bias from the agent that wrote the code. In this case it’s not Matt Pocock’s skill being called so maybe the Claude Code version does this automatically.

Let’s see if the basic functions for the app are working in the browser…

uh-huh

whole stack.. lol..

No menu so lets throw caution to the wind and let Claude access my browser…

and it’s noticed there’s no menu navigation…

and it’s off to races…

Oh wow, working with the browser extension is amazing.

and…

Incredible!

Let’s add those missing nav links…

Some more live testing in the browser now the nav links have been added…

Amazing.

Tomorrow, I’ll test it all works for a human with real life projects and tasks.

The first issue has been implemented, tested and committed. Now another issue can be implemented in the codebase…

Going with issue #4…

Code review seems to be taking a looong time…

OK… it had got stuck…

All done…

Note: I discovered later that the /code-review skill that runs is the Claude built in skill and not the Matt Pocock one. I need to change this for the next project.

Moving on with the issues list… number three – Team management…

and done…

Now onto #5 CRUD and access control

All done….

… and onto #6

All done and onto #7 … … and done…

Oh.. had to restart my PC and Claude Code got confused where it was so I asked for a review and….

On to #8 – the timer… … and it’s done

Next up, let’s see if something will actually run in the browser.

All the tickets are ready for agents…

First need to clear the context to not fill the context window with tokens and affect the quality of the output and waste token use.

/clear

Now we are ready to start work on the code itself…

Implement issue #2…

the /code-review agent found some issues…

Fixed them, retested and now issue 2 has been implemented…

and is ready to commit…

ta da!…

Harvest (app) put their prices up to silly levels after the Bending Spoons acquisition so I cancelled the renewal and started my own time tracking and invoicing application based on Laravel, developing with Claude Code following Matt Pocock’s tutorials on YouTube.

So far, I’ve used the /grill-with-docs for a Q&A with the AI and then /to-spec to get the first issue here https://github.com/robotzero1/gather-app/issues/1

Next up – using the /to-tickets Skill to create the Github issues for the agent to work through.