CodeAFHand a job to a specialist

Hand a job to a specialist

Talk a change through in any chat, then say "give this to senior-dev" and the chat hands the job over with everything it found.

Think in the chat, build with the specialist. The hand-off should carry what the conversation already learned.
  • give this to senior-dev
  • the fix we just found
  • done properly
  • a feature with its tests

A conversation is a good place to work out what a change should be: you ask questions, the chat reads the code, and you settle what done means. Doing the change is a different job. senior-dev, the coding specialist, takes one whole change and carries it alone to a checked result. You do not have to start over to use it: name it in the conversation, and the chat hands the job over.

Try it in CodeAF

Where

In the conversation where you discussed the change.

Type
Give this to senior-dev: make Store.add store the title with surrounding whitespace stripped, and add a test for it.

Then press Enter.

You see

The chat checks the code and writes the brief. Then it asks wants to start a [senior-dev] task: Test title whitespace stripping in Store.add.

The chat writes the brief

Name senior-dev and press Enter; the chat reads the code, says what it found, and asks to start the task. Keys: Give this to senior-dev: make Store.add store the title with surrounding whitespace stripped, and add a test for it.Enter

Before it hands over, the chat looks at what you asked for. In our run it found that Store.add already stripped the title and only the test was missing, said so, and wrote the brief for the test alone. senior-dev then left the code as it was and added just the test.

The card says where the work goes and what it may spend: where: <your folder>, on a branch of its own, up to $10.00 and 3h, the model, and ctrl+e for the brief. 1 start it is recommended and it starts on its own unless you say otherwise; any key stops the clock, so you can read the brief first. Typing /senior-dev with a brief instead starts it at once, with no card.

When it lands

Enter starts it; the run wears its badge, lands on a branch of its own, and the chat offers the merge. Keys: Enter

The task wears the [senior-dev] badge in the Tasks column while it runs. It ends on a card like ◆ Test title whitespace stripping in Store.add · done · 31s · 1 file · branch kept · task/test-title-whitespace-stripping-d3db9d, followed by senior-dev's ending went to the chat. The chat reads the ending for you: here it confirmed the suite passed, said your main branch was untouched, and asked Want me to merge it into main?

Things to build

  • Investigate, then delegate: ask the chat why a test fails, agree on the fix, then say "give this to senior-dev": the brief carries what the chat found.
  • The fix, done properly: "Give this to senior-dev: the fix we just found, with a test for it." It lands on its own branch and the chat asks whether to merge.
  • A review line for main: one team member hands each change to senior-dev, another reads the branch and runs the tests, and the manager merges only on a pass. Review every change

Go further

Review every change: Every change is built on its own branch, checked by a reviewer, and merged only on a pass.

Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.