CodeAFBring your skills

Bring your skills

Skill folders you already wrote for other tools shape CodeAF's work in place, team members included.

Your team's habits are written down once. Every agent should follow them.
  • how we write tests
  • a changelog line per change
  • the commit message format

A skill is a short file that teaches an agent how your project does something: how tests are laid out, how a changelog line reads. If you already keep skills in a repository for another tool, CodeAF reads them where they are. Nothing is copied or converted, the skills are used without being named, and every member of a team follows them too.

Steps

  1. Keep your skills where they already are: .claude/skills/<name>/SKILL.md or .codex/skills/<name>/SKILL.md in the repository. Our repository had two:
    • changelog-entry, which says to append one line under ## Unreleased after any finished change, ending in (skill: changelog-entry).
    • go-table-tests, which asks for table-driven tests with at least four cases, t.Run, and a header line naming the skill.
  2. Run codeaf in the repository. Skills are read at launch.
  3. Type /skill and press Enter. Both are listed with their descriptions and the word shelf.
  4. Ask for work without naming a skill:
Add more tests for Caesar and Rot13 in a new file cipher_test.go.

What you see

The turn shows which skills it used, skills · go-table-tests, changelog-entry. The new cipher_test.go is table-driven, with 8 cases for one function and 6 for the other, t.Run, and the header line. CHANGELOG.md gets exactly one new line, ending in (skill: changelog-entry).

Skills reach teams as well. We made a team of two chats on the wall (Alt+V, Space on each, S), gave it a manager, and asked it to split a runnable example for each of the 20 issues between its two members, each following the changelog-entry skill when done. The manager sent two directives, both members wrote their halves of docs/EXAMPLES.md, and the changelog gained - [textkit] Add runnable examples for issues 1-10 to docs/EXAMPLES.md (skill: changelog-entry).

In our run

The solo chat took 5 minutes and 38 seconds and cost $0.07. The team's round took about 3 minutes and cost $0.12.

Make it yours

  • Write down one habit. Start with the rule you repeat most in reviews: a commit message format, where fixtures live, how errors are wrapped. One short SKILL.md is enough.
  • Mix the folders. Both skill folders are read side by side. Our run used one skill from each in the same turn, with no setting to change.
  • Make the team follow it. Name the skill in a manager's brief, as we did, and the members it hands work to follow it too.

Go further

Teams: Named, coloured groups of agents, gathered around the outcome they serve.

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