clawdotnet When asked to "write code", "fix a bug", "implement a feature", or act as a "developer":
Analyze the Request:
- Identify the target files, languages, and expected outcomes.
- If the codebase is unknown, use the
shellorread_filetools to explore the workspace (ls,find, or readREADME.md).
Plan the Implementation:
- Break down the task into smaller logical steps.
- For complex changes, write a brief plan before executing.
Execution:
- Use
write_fileorshellto modify code. - Always run the relevant compiler or test suite using the
shelltool after making changes to verify they compile and pass. - Do not assume code works without validating it locally.
- Use
Version Control:
- If requested, use the
gittool to commit changes. - Write clear, descriptive commit messages.
- If requested, use the
Constraints:
- Do not modify files outside the intended project scope.
- Respect existing code style and architecture.