MCPcopy Index your code
hub / github.com/kirodotdev/Kiro / buildCommentPrompt

Function buildCommentPrompt

scripts/bedrock_comment_generator.ts:91–133  ·  view source on GitHub ↗

* Build prompt for generating acknowledgment comment

(
  issueTitle: string,
  issueBody: string,
  issueComments: string,
  labels: string
)

Source from the content-addressed store, hash-verified

89 * Build prompt for generating acknowledgment comment
90 */
91function buildCommentPrompt(
92 issueTitle: string,
93 issueBody: string,
94 issueComments: string,
95 labels: string
96): string {
97 return `You are a friendly GitHub bot for the Kiro project. Generate a welcoming acknowledgment comment for a newly triaged issue.
98
99===== ISSUE TITLE =====
100${issueTitle}
101===== END ISSUE TITLE =====
102
103===== ISSUE BODY =====
104${issueBody || "(No description provided)"}
105===== END ISSUE BODY =====
106
107===== EXISTING COMMENTS =====
108${issueComments}
109===== END EXISTING COMMENTS =====
110
111===== ASSIGNED LABELS =====
112${labels}
113===== END LABELS =====
114
115TASK:
116Write a brief, friendly acknowledgment comment (2-4 sentences) that:
1171. Thanks the user for opening the issue
1182. Briefly acknowledges what the issue is about (in 1 sentence), considering any discussion in the comments
1193. Mentions that a maintainer will review it shortly
1204. Is warm and encouraging
121
122RULES:
123- Keep it concise (2-4 sentences max)
124- Be friendly and professional
125- Don't make promises about fixes or timelines
126- Don't repeat the issue title verbatim
127- Use a conversational tone
128- End with an encouraging note
129- If there are existing comments, acknowledge the discussion briefly
130
131OUTPUT:
132Provide ONLY the comment text, no JSON, no formatting markers.`;
133}
134
135/**
136 * Invoke Bedrock model with automatic fallback

Callers 1

Calls

no outgoing calls

Tested by

no test coverage detected