You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When undertaking a task, take a moment to pause and ask the user what the intent of the task is. Use this to write the best code to fix the problem or implement the feature.
4
+
5
+
## Code formatting
6
+
7
+
We always write JavaScript with double quotes and two spaces for indentation, so when your responses include JavaScript code, please follow those conventions.
8
+
9
+
Go code is written in the style of the standard library. When possible, tests are table-driven tests.
10
+
11
+
All code is formatted with prettier on save, but to run formatting yourself:
12
+
13
+
```
14
+
npm run format
15
+
```
16
+
17
+
## Commit Message Format
18
+
19
+
Always use conventional commit format for all commit messages. The format should be:
20
+
21
+
```
22
+
<type>[optional scope]: <description>
23
+
24
+
[optional body]
25
+
26
+
[optional footer(s)]
27
+
```
28
+
29
+
### Types
30
+
31
+
-`feat`: A new feature
32
+
-`fix`: A bug fix
33
+
-`docs`: Documentation only changes
34
+
-`style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
35
+
-`refactor`: A code change that neither fixes a bug nor adds a feature
36
+
-`perf`: A code change that improves performance
37
+
-`test`: Adding missing tests or correcting existing tests
38
+
-`build`: Changes that affect the build system or external dependencies
39
+
-`ci`: Changes to our CI configuration files and scripts
40
+
-`chore`: Other changes that don't modify src or test files
41
+
-`revert`: Reverts a previous commit
42
+
43
+
### Examples
44
+
45
+
-`feat: add user authentication`
46
+
-`fix: resolve memory leak in data processing`
47
+
-`docs: update API documentation`
48
+
-`ci: update GitHub Actions workflows`
49
+
-`refactor: simplify user service logic`
50
+
51
+
### Breaking Changes
52
+
53
+
For breaking changes, add `!` after the type/scope:
54
+
55
+
-`feat!: change API response format`
56
+
-`fix(api)!: remove deprecated endpoint`
57
+
58
+
Or add `BREAKING CHANGE:` in the footer:
59
+
60
+
```
61
+
feat: add new user service
62
+
63
+
BREAKING CHANGE: User API now requires authentication tokens
64
+
```
65
+
66
+
### How to commit
67
+
68
+
When committing, make sure to use double quotes around your commit message, sign off the commit as:
69
+
70
+
```
71
+
Mimi Yasomi <mimi@xeserv.us>
72
+
```
73
+
74
+
Make sure Mimi is the author too.
75
+
76
+
Write your commit to a temporary file before committing. Be sure to use the printf command because you're in fish.
0 commit comments