bitbucket-gemini-action 1.0.9 → 1.0.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js CHANGED
@@ -2320,7 +2320,11 @@ ${formatComments(context.comments)}` : ""}
2320
2320
 
2321
2321
  **모든 코멘트와 피드백은 반드시 한국어로 작성하세요.**
2322
2322
 
2323
- 특정 라인에 인라인 코멘트를 남기고, 전체적인 피드백은 요약 코멘트로 작성하세요.`;
2323
+ ## 중요: 도구 사용 방법
2324
+ 1. **create_inline_comment**: 코드의 특정 라인에 피드백을 남길 때 반드시 이 도구를 사용하세요. 개선이 필요한 각 코드 라인마다 개별적으로 호출하세요.
2325
+ 2. **create_pr_comment**: 전체적인 요약만 이 도구로 작성하세요.
2326
+
2327
+ 피드백이 있는 모든 코드 라인에 대해 create_inline_comment를 사용해야 합니다.`;
2324
2328
  }
2325
2329
  function buildTagModePrompt(context, userMessage, mentionAuthor) {
2326
2330
  const filesSummary = context.files.map((f) => `- ${f.path} (${f.status}): +${f.additions}/-${f.deletions}`).join(`
@@ -2462,7 +2466,7 @@ ${presetPrompt}`;
2462
2466
  // src/gemini/tools.ts
2463
2467
  var createInlineCommentTool = {
2464
2468
  name: "create_inline_comment",
2465
- description: "Create an inline comment on a specific line of code in the pull request. Use this to provide targeted feedback on specific code changes.",
2469
+ description: "Create an inline comment on a specific line of code in the pull request. Use this tool for each line where you have feedback. This is the PRIMARY tool for code review comments.",
2466
2470
  parameters: {
2467
2471
  type: "object",
2468
2472
  properties: {
@@ -2472,11 +2476,11 @@ var createInlineCommentTool = {
2472
2476
  },
2473
2477
  line: {
2474
2478
  type: "number",
2475
- description: "The line number to comment on (1-indexed)"
2479
+ description: "The NEW file line number from the diff (the number after '+' in the diff). For example, in '@@ -0,0 +5,7 @@', if you want to comment on the line shown as '+ - step:', look at the line numbers in the NEW file section (right side). The first added line would be line 5, second would be 6, etc."
2476
2480
  },
2477
2481
  content: {
2478
2482
  type: "string",
2479
- description: "The comment content in markdown format. Be specific and actionable."
2483
+ description: "The comment content in markdown format. Be specific and actionable. Write in Korean."
2480
2484
  }
2481
2485
  },
2482
2486
  required: ["path", "line", "content"]
@@ -3420,7 +3420,11 @@ ${formatComments2(context.comments)}` : ""}
3420
3420
 
3421
3421
  **모든 코멘트와 피드백은 반드시 한국어로 작성하세요.**
3422
3422
 
3423
- 특정 라인에 인라인 코멘트를 남기고, 전체적인 피드백은 요약 코멘트로 작성하세요.`;
3423
+ ## 중요: 도구 사용 방법
3424
+ 1. **create_inline_comment**: 코드의 특정 라인에 피드백을 남길 때 반드시 이 도구를 사용하세요. 개선이 필요한 각 코드 라인마다 개별적으로 호출하세요.
3425
+ 2. **create_pr_comment**: 전체적인 요약만 이 도구로 작성하세요.
3426
+
3427
+ 피드백이 있는 모든 코드 라인에 대해 create_inline_comment를 사용해야 합니다.`;
3424
3428
  }
3425
3429
  function buildTagModePrompt(context, userMessage, mentionAuthor) {
3426
3430
  const filesSummary = context.files.map((f) => `- ${f.path} (${f.status}): +${f.additions}/-${f.deletions}`).join(`
@@ -3562,7 +3566,7 @@ ${presetPrompt}`;
3562
3566
  // src/gemini/tools.ts
3563
3567
  var createInlineCommentTool = {
3564
3568
  name: "create_inline_comment",
3565
- description: "Create an inline comment on a specific line of code in the pull request. Use this to provide targeted feedback on specific code changes.",
3569
+ description: "Create an inline comment on a specific line of code in the pull request. Use this tool for each line where you have feedback. This is the PRIMARY tool for code review comments.",
3566
3570
  parameters: {
3567
3571
  type: "object",
3568
3572
  properties: {
@@ -3572,11 +3576,11 @@ var createInlineCommentTool = {
3572
3576
  },
3573
3577
  line: {
3574
3578
  type: "number",
3575
- description: "The line number to comment on (1-indexed)"
3579
+ description: "The NEW file line number from the diff (the number after '+' in the diff). For example, in '@@ -0,0 +5,7 @@', if you want to comment on the line shown as '+ - step:', look at the line numbers in the NEW file section (right side). The first added line would be line 5, second would be 6, etc."
3576
3580
  },
3577
3581
  content: {
3578
3582
  type: "string",
3579
- description: "The comment content in markdown format. Be specific and actionable."
3583
+ description: "The comment content in markdown format. Be specific and actionable. Write in Korean."
3580
3584
  }
3581
3585
  },
3582
3586
  required: ["path", "line", "content"]
@@ -2319,7 +2319,11 @@ ${formatComments(context.comments)}` : ""}
2319
2319
 
2320
2320
  **모든 코멘트와 피드백은 반드시 한국어로 작성하세요.**
2321
2321
 
2322
- 특정 라인에 인라인 코멘트를 남기고, 전체적인 피드백은 요약 코멘트로 작성하세요.`;
2322
+ ## 중요: 도구 사용 방법
2323
+ 1. **create_inline_comment**: 코드의 특정 라인에 피드백을 남길 때 반드시 이 도구를 사용하세요. 개선이 필요한 각 코드 라인마다 개별적으로 호출하세요.
2324
+ 2. **create_pr_comment**: 전체적인 요약만 이 도구로 작성하세요.
2325
+
2326
+ 피드백이 있는 모든 코드 라인에 대해 create_inline_comment를 사용해야 합니다.`;
2323
2327
  }
2324
2328
  function buildTagModePrompt(context, userMessage, mentionAuthor) {
2325
2329
  const filesSummary = context.files.map((f) => `- ${f.path} (${f.status}): +${f.additions}/-${f.deletions}`).join(`
@@ -2461,7 +2465,7 @@ ${presetPrompt}`;
2461
2465
  // src/gemini/tools.ts
2462
2466
  var createInlineCommentTool = {
2463
2467
  name: "create_inline_comment",
2464
- description: "Create an inline comment on a specific line of code in the pull request. Use this to provide targeted feedback on specific code changes.",
2468
+ description: "Create an inline comment on a specific line of code in the pull request. Use this tool for each line where you have feedback. This is the PRIMARY tool for code review comments.",
2465
2469
  parameters: {
2466
2470
  type: "object",
2467
2471
  properties: {
@@ -2471,11 +2475,11 @@ var createInlineCommentTool = {
2471
2475
  },
2472
2476
  line: {
2473
2477
  type: "number",
2474
- description: "The line number to comment on (1-indexed)"
2478
+ description: "The NEW file line number from the diff (the number after '+' in the diff). For example, in '@@ -0,0 +5,7 @@', if you want to comment on the line shown as '+ - step:', look at the line numbers in the NEW file section (right side). The first added line would be line 5, second would be 6, etc."
2475
2479
  },
2476
2480
  content: {
2477
2481
  type: "string",
2478
- description: "The comment content in markdown format. Be specific and actionable."
2482
+ description: "The comment content in markdown format. Be specific and actionable. Write in Korean."
2479
2483
  }
2480
2484
  },
2481
2485
  required: ["path", "line", "content"]
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bitbucket-gemini-action",
3
- "version": "1.0.9",
3
+ "version": "1.0.11",
4
4
  "description": "Bitbucket Pipeline action for AI-powered code review using Google Gemini",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",