Update agent compile guidance
This commit is contained in:
@@ -13,6 +13,7 @@ Also see the other related technical documentation in the docs folder.
|
||||
- Always place each newly created class into its own file. The file name must match the class name.
|
||||
- When asked to begin working on a task, create a detailed implementation plan first, present the plan to the user, and ask for approval before beginning with the actual implementation.
|
||||
- When an task is finished, perform a code review to evaluate if the change is clean and maintainable with high software engineering standards. Iterate on the code and repeat the review process until satisfied.
|
||||
- Check if the code compiles with a compile-only `dotnet build` to avoid artifact conflicts.
|
||||
- After the implementation is finished, verify all changed files, and run `python D:\Code\crlf.py $file1 $file2 ...` only for files you recognize, in order to normalize all line endings of all touched files to CRLF.
|
||||
- If there's documnentation present, always keep it updated.
|
||||
- At the end perform a git commit with a one-liner summary.
|
||||
Reference in New Issue
Block a user