Let's start adding the issue number to the branch name

Author: wspringer

.claude/commands/fix-gh-issue.md

@@ -9,12 +9,13 @@ Follow these steps:
 3. Search the codebase for relevant files
 4. Start developing the issue by creating a branch using `gh issue develop -c
 {issue number} --name {branch name}`, taking the issue number from the
-   arguments, using a sensible branch name.
-5. Implement the necessary changes to fix the issue
-6. Write and run tests to verify the fix
-7. Ensure code passes linting and type checking
-8. Check if the README is still correct, given the changes. Correct when needed.
-9. Determine if this should be considered a patch, a minor or a major change,
+   arguments, using a sensible branch name. Include the issue number in the
+   branch name, at the end.
+1. Implement the necessary changes to fix the issue
+2. Write and run tests to verify the fix
+3. Ensure code passes linting and type checking
+4. Check if the README is still correct, given the changes. Correct when needed.
+5. Determine if this should be considered a patch, a minor or a major change,
    and ask me for confirmation.
-10. Document the change in a changeset, following knope's convention of having
+6.  Document the change in a changeset, following knope's convention of having
    changesets.