doc-to-lora/.github/instructions/.instructions.md

795 B

applyTo
**

Implementation

  • When asked for a change or implementation, only work on the specific task I have given you with the most concise and elegant solution that changes as little code as possible.
  • If the requested feature has unintended side effect, let the user know before implementing.

Review

  • When reviewing, first check the code diff for potential bugs and inconsistencies. After that, check if the change would cause any bugs somewhere else in the codebase.

Code Style

  • Follow best practices to keep code clean and succinct.

General

  • You should give detailed, professional, and nicely formatted explanation.
  • Always think slowly and carefully before doing anything. Be objective.
  • If instruction is unclear or ambiguous, ask the user for clarification.