@polka-codes/core 0.9.24 → 0.9.25

package/dist/_tsup-dts-rollup.d.ts

@@ -774,7 +774,7 @@ export declare const default_alias_3: {
 export declare const default_alias_4: {
     readonly name: "reviewDiff";
     readonly description: "Reviews a git diff";
-    readonly prompt: "\n# Code Review Prompt\n\nYou are a senior software engineer reviewing code changes.\n\n## Critical Instructions\n**ONLY review the actual changes shown in the diff.** Do not comment on existing code that wasn't modified.\n\n## Viewing Changes\n- **Use git_diff** to inspect the actual code changes for each relevant file.\n  - **Pull request**: use the provided commit range for the git_diff tool with contextLines: 5 and includeLineNumbers: true\n  - **Local changes**: diff staged or unstaged files using the git_diff tool with contextLines: 5 and includeLineNumbers: true\n- The diff will include line number annotations: [Line N] for additions and [Line N removed] for deletions\n- If a pull request is present you may receive:\n  - <pr_title>\n  - <pr_description>\n  - <commit_messages>\n- A <review_instructions> tag tells you the focus of the review.\n- File status information is provided in <file_status> - use this to understand which files were modified, added, deleted, or renamed.\n\n## Line Number Reporting\n- **IMPORTANT**: Use the line numbers from the annotations in the diff output\n- For additions: Look for [Line N] annotations after the + lines\n- For deletions: Look for [Line N removed] annotations after the - lines\n- For modifications: Report the line number of the new/current code (from [Line N] annotations)\n- Report single lines as \"N\" and ranges as \"N-M\"\n\n## Review Guidelines\nFocus exclusively on the changed lines (+ additions, - deletions, modified lines):\n- **Specific issues**: Point to exact problems in the changed code with accurate line references from the annotations\n- **Actionable fixes**: Provide concrete solutions, not vague suggestions\n- **Clear reasoning**: Explain why each issue matters and how to fix it\n- **Avoid generic advice**: No generic suggestions like \"add more tests\", \"improve documentation\", or \"follow best practices\" unless directly related to a specific problem in the diff\n\n## What NOT to review\n- Existing unchanged code\n- Overall project structure or architecture (unless directly impacted by changes)\n- Generic best practices unrelated to the specific changes\n- Missing features or functionality not part of this diff\n\n## Output Format\nDo **not** include praise or positive feedback. Ignore generated files such as lock files.\nOnly include reviews for actual issues found in the changed code.\n\nReturn your review as a JSON object inside a ```json block, wrapped like:\n<tool_attempt_completion>\n<tool_parameter_result>\n```json\n{\n  \"overview\": \"Summary of specific issues found in the diff changes, or 'No issues found' if the changes look good.\",\n  \"specificReviews\": [\n    {\n      \"file\": \"path/filename.ext\",\n      \"lines\": \"N or N-M\",\n      \"review\": \"Specific issue with the changed code and exact actionable fix.\"\n    }\n  ]\n}\n```\n</tool_parameter_result>\n</tool_attempt_completion>\n";
+    readonly prompt: "\n# Code Review Prompt\n\nYou are a senior software engineer reviewing code changes.\n\n## Critical Instructions\n- **ONLY review the actual changes shown in the diff.** Do not comment on existing code that wasn't modified.\n- **ONLY run git_diff on files that are reviewable source/config files** per the \"File Selection for git_diff\" rules below. Do not pass excluded files to git_diff.\n\n## File Selection for git_diff\nUse <file_status> to decide which files to diff. Include only files likely to contain human-authored source or meaningful configuration.\n\nInclude (run git_diff):\n- Application/source code\n- UI/templates/assets code\n- Infra/config that affects behavior\n\nExclude (do NOT run git_diff; do not review):\n- Lockfiles\n- Generated/build artifacts & deps\n- Test artifacts/snapshots\n- Data and fixtures\n- Binary/media/minified/maps\n\n## Viewing Changes\n- For each included file, **use git_diff** to inspect the actual code changes:\n  - **Pull request:** use the provided commit range for the git_diff tool with contextLines: 5 and includeLineNumbers: true, but only surface and review the included files.\n  - **Local changes:** diff staged or unstaged included files using git_diff with contextLines: 5 and includeLineNumbers: true.\n- The diff will include line number annotations: [Line N] for additions and [Line N removed] for deletions.\n- You may receive:\n  - <pr_title>\n  - <pr_description>\n  - <commit_messages>\n- A <review_instructions> tag tells you the focus of the review.\n- Use <file_status> to understand which files were modified, added, deleted, or renamed and to apply the inclusion/exclusion rules above.\n\n## Line Number Reporting\n- Use the line numbers from the annotations in the diff output.\n- For additions: use the number from the [Line N] annotation after the + line.\n- For deletions: use the number from the [Line N removed] annotation after the - line.\n- For modifications: report the line number of the new/current code (from [Line N]).\n- Report single lines as \"N\" and ranges as \"N-M\".\n\n## Review Guidelines\nFocus exclusively on the changed lines (+ additions, - deletions, modified lines):\n- **Specific issues:** Point to exact problems in the changed code with accurate line references from the annotations.\n- **Actionable fixes:** Provide concrete solutions, not vague suggestions.\n- **Clear reasoning:** Explain why each issue matters and how to fix it.\n- **Avoid generic advice** unless directly tied to a specific problem visible in the diff.\n\n## What NOT to review\n- Files excluded by the \"File Selection for git_diff\" rules (do not diff or comment on them).\n- Existing unchanged code.\n- Overall project structure/architecture unless directly impacted by the changes.\n- Missing features or functionality not part of this diff.\n\n## Output Format\nDo not include praise or positive feedback.\nOnly include reviews for actual issues found in the changed code.\n\nReturn your review as a JSON object inside a ```json block, wrapped like:\n<tool_attempt_completion>\n<tool_parameter_result>\n```json\n{\n  \"overview\": \"Summary of specific issues found in the diff changes, 'No issues found', or 'No reviewable changes' if all modified files were excluded.\",\n  \"specificReviews\": [\n    {\n      \"file\": \"path/filename.ext\",\n      \"lines\": \"N or N-M\",\n      \"review\": \"Specific issue with the changed code and exact actionable fix.\"\n    }\n  ]\n}\n```\n</tool_parameter_result>\n</tool_attempt_completion>\n";
     readonly formatInput: (params: Input_2) => string;
     readonly parseOutput: (output: string) => Output_2;
     readonly agent: (options: SharedAgentOptions) => AnalyzerAgent;
@@ -787,7 +787,7 @@ export declare const default_alias_5: {
         readonly parameters: z.ZodObject<{
             staged: z.ZodPipe<z.ZodTransform<unknown, unknown>, z.ZodDefault<z.ZodOptional<z.ZodBoolean>>>;
             commitRange: z.ZodOptional<z.ZodString>;
-            file: z.ZodOptional<z.ZodString>;
+            file: z.ZodString;
             contextLines: z.ZodDefault<z.ZodOptional<z.ZodCoercedNumber<unknown>>>;
             includeLineNumbers: z.ZodPipe<z.ZodTransform<unknown, unknown>, z.ZodDefault<z.ZodOptional<z.ZodBoolean>>>;
         }, z.core.$strip>;
@@ -799,7 +799,7 @@ export declare const default_alias_5: {
     parameters: z.ZodObject<{
         staged: z.ZodPipe<z.ZodTransform<unknown, unknown>, z.ZodDefault<z.ZodOptional<z.ZodBoolean>>>;
         commitRange: z.ZodOptional<z.ZodString>;
-        file: z.ZodOptional<z.ZodString>;
+        file: z.ZodString;
         contextLines: z.ZodDefault<z.ZodOptional<z.ZodCoercedNumber<unknown>>>;
         includeLineNumbers: z.ZodPipe<z.ZodTransform<unknown, unknown>, z.ZodDefault<z.ZodOptional<z.ZodBoolean>>>;
     }, z.core.$strip>;
@@ -1545,7 +1545,7 @@ export declare const toolInfo: {
     readonly parameters: z.ZodObject<{
         staged: z.ZodPipe<z.ZodTransform<unknown, unknown>, z.ZodDefault<z.ZodOptional<z.ZodBoolean>>>;
         commitRange: z.ZodOptional<z.ZodString>;
-        file: z.ZodOptional<z.ZodString>;
+        file: z.ZodString;
         contextLines: z.ZodDefault<z.ZodOptional<z.ZodCoercedNumber<unknown>>>;
         includeLineNumbers: z.ZodPipe<z.ZodTransform<unknown, unknown>, z.ZodDefault<z.ZodOptional<z.ZodBoolean>>>;
     }, z.core.$strip>;

package/dist/index.js

@@ -3733,7 +3733,7 @@ var toolInfo15 = {
       return val;
     }, z17.boolean().optional().default(false)).describe("Get staged changes instead of unstaged changes."),
     commitRange: z17.string().optional().describe('The commit range to get the diff for (e.g., "main...HEAD").'),
-    file: z17.string().optional().describe("Get the diff for a specific file."),
+    file: z17.string().describe("Get the diff for a specific file."),
     contextLines: z17.coerce.number().optional().default(5).describe("Number of context lines to include around changes."),
     includeLineNumbers: z17.preprocess((val) => {
       if (typeof val === "string") {
@@ -3828,42 +3828,58 @@ var prompt5 = `
 You are a senior software engineer reviewing code changes.
 
 ## Critical Instructions
-**ONLY review the actual changes shown in the diff.** Do not comment on existing code that wasn't modified.
+- **ONLY review the actual changes shown in the diff.** Do not comment on existing code that wasn't modified.
+- **ONLY run git_diff on files that are reviewable source/config files** per the "File Selection for git_diff" rules below. Do not pass excluded files to git_diff.
+
+## File Selection for git_diff
+Use <file_status> to decide which files to diff. Include only files likely to contain human-authored source or meaningful configuration.
+
+Include (run git_diff):
+- Application/source code
+- UI/templates/assets code
+- Infra/config that affects behavior
+
+Exclude (do NOT run git_diff; do not review):
+- Lockfiles
+- Generated/build artifacts & deps
+- Test artifacts/snapshots
+- Data and fixtures
+- Binary/media/minified/maps
 
 ## Viewing Changes
-- **Use git_diff** to inspect the actual code changes for each relevant file.
-  - **Pull request**: use the provided commit range for the git_diff tool with contextLines: 5 and includeLineNumbers: true
-  - **Local changes**: diff staged or unstaged files using the git_diff tool with contextLines: 5 and includeLineNumbers: true
-- The diff will include line number annotations: [Line N] for additions and [Line N removed] for deletions
-- If a pull request is present you may receive:
+- For each included file, **use git_diff** to inspect the actual code changes:
+  - **Pull request:** use the provided commit range for the git_diff tool with contextLines: 5 and includeLineNumbers: true, but only surface and review the included files.
+  - **Local changes:** diff staged or unstaged included files using git_diff with contextLines: 5 and includeLineNumbers: true.
+- The diff will include line number annotations: [Line N] for additions and [Line N removed] for deletions.
+- You may receive:
   - <pr_title>
   - <pr_description>
   - <commit_messages>
 - A <review_instructions> tag tells you the focus of the review.
-- File status information is provided in <file_status> - use this to understand which files were modified, added, deleted, or renamed.
+- Use <file_status> to understand which files were modified, added, deleted, or renamed and to apply the inclusion/exclusion rules above.
 
 ## Line Number Reporting
-- **IMPORTANT**: Use the line numbers from the annotations in the diff output
-- For additions: Look for [Line N] annotations after the + lines
-- For deletions: Look for [Line N removed] annotations after the - lines
-- For modifications: Report the line number of the new/current code (from [Line N] annotations)
-- Report single lines as "N" and ranges as "N-M"
+- Use the line numbers from the annotations in the diff output.
+- For additions: use the number from the [Line N] annotation after the + line.
+- For deletions: use the number from the [Line N removed] annotation after the - line.
+- For modifications: report the line number of the new/current code (from [Line N]).
+- Report single lines as "N" and ranges as "N-M".
 
 ## Review Guidelines
 Focus exclusively on the changed lines (+ additions, - deletions, modified lines):
-- **Specific issues**: Point to exact problems in the changed code with accurate line references from the annotations
-- **Actionable fixes**: Provide concrete solutions, not vague suggestions
-- **Clear reasoning**: Explain why each issue matters and how to fix it
-- **Avoid generic advice**: No generic suggestions like "add more tests", "improve documentation", or "follow best practices" unless directly related to a specific problem in the diff
+- **Specific issues:** Point to exact problems in the changed code with accurate line references from the annotations.
+- **Actionable fixes:** Provide concrete solutions, not vague suggestions.
+- **Clear reasoning:** Explain why each issue matters and how to fix it.
+- **Avoid generic advice** unless directly tied to a specific problem visible in the diff.
 
 ## What NOT to review
-- Existing unchanged code
-- Overall project structure or architecture (unless directly impacted by changes)
-- Generic best practices unrelated to the specific changes
-- Missing features or functionality not part of this diff
+- Files excluded by the "File Selection for git_diff" rules (do not diff or comment on them).
+- Existing unchanged code.
+- Overall project structure/architecture unless directly impacted by the changes.
+- Missing features or functionality not part of this diff.
 
 ## Output Format
-Do **not** include praise or positive feedback. Ignore generated files such as lock files.
+Do not include praise or positive feedback.
 Only include reviews for actual issues found in the changed code.
 
 Return your review as a JSON object inside a \`\`\`json block, wrapped like:
@@ -3871,7 +3887,7 @@ Return your review as a JSON object inside a \`\`\`json block, wrapped like:
 <tool_parameter_result>
 \`\`\`json
 {
-  "overview": "Summary of specific issues found in the diff changes, or 'No issues found' if the changes look good.",
+  "overview": "Summary of specific issues found in the diff changes, 'No issues found', or 'No reviewable changes' if all modified files were excluded.",
   "specificReviews": [
     {
       "file": "path/filename.ext",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polka-codes/core",
-  "version": "0.9.24",
+  "version": "0.9.25",
   "license": "AGPL-3.0",
   "author": "github@polka.codes",
   "type": "module",