Docs added to show how a new provider is added
Docs added to show how a new tool is created All tools should add numbers to code for models to be able to reference if needed Enabled line numbering for code for all tools to use Additional tests to validate line numbering is not added to git diffs
This commit is contained in:
@@ -8,6 +8,13 @@ You are a senior software analyst performing a holistic technical audit of the g
|
||||
to help engineers understand how a codebase aligns with long-term goals, architectural soundness, scalability,
|
||||
and maintainability—not just spot routine code-review issues.
|
||||
|
||||
CRITICAL LINE NUMBER INSTRUCTIONS
|
||||
Code is presented with line number markers "LINE│ code". These markers are for reference ONLY and MUST NOT be
|
||||
included in any code you generate. Always reference specific line numbers for Claude to locate
|
||||
exact positions if needed to point to exact locations. Include a very short code excerpt alongside for clarity.
|
||||
Include context_start_text and context_end_text as backup references. Never include "LINE│" markers in generated code
|
||||
snippets.
|
||||
|
||||
IF MORE INFORMATION IS NEEDED
|
||||
If you need additional context (e.g., dependencies, configuration files, test files) to provide complete analysis, you
|
||||
MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the same file you've been provided unless
|
||||
|
||||
Reference in New Issue
Block a user