@qelos/aidev 0.7.2 → 0.7.3

package/dist/commands/init.js

@@ -367,111 +367,111 @@ function printGhSuggestion(remote) {
     console.log(`  PRs will be created automatically after pushing branches.`);
     console.log();
 }
-const HOOKS_BOILERPLATE = `// aidev hooks — customize the AI task automation pipeline
-//
-// Each export below is an async (context, vm) hook. Return a new/updated context object to
-// change prompts, subtasks, etc.; return nothing to keep the incoming context. Throw to abort
-// the current step (whole run, single task, conflict resolution, etc., depending on the hook).
-//
-// vm: run AI (first available agent), postComment, updateStatus, getComments, log.info/warn/error
-//
-// .ts files are loaded via jiti — no TypeScript compiler or toolchain needed.
-
-// ─── Context types (mirror aidev's internal shapes — tweak here for editor hints) ─
-
-interface RunContext {
-  config: Record<string, unknown>;
-  filter: string;
-  taskCount: number;
-}
-
-interface TaskContext {
-  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
-  config: Record<string, unknown>;
-  branchName: string;
-  prompt: string;
-}
-
-interface ResolveConflictsContext {
-  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
-  config: Record<string, unknown>;
-  branchName: string;
-  conflictFiles: string[];
-  prompt: string;
-}
-
-interface NonCodeTaskContext {
-  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
-  config: Record<string, unknown>;
-  prompt: string;
-}
-
-interface ThinkingTaskContext {
-  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
-  config: Record<string, unknown>;
-  branchName: string;
-  subtasks: Array<{ id: number; title: string; description: string; status: string }>;
-}
-
-interface HookVM {
-  runAI(prompt: string): Promise<{ success: boolean; output: string; error: string }>;
-  postComment(taskId: string, text: string): Promise<void>;
-  updateStatus(taskId: string, status: string): Promise<void>;
-  getComments(taskId: string): Promise<Array<{ id: string; text: string; author: string }>>;
-  log: { info(msg: string): void; warn(msg: string): void; error(msg: string): void };
-}
-
-// ─── Hooks (fill in — ask an AI: "implement beforeEachTask to append X to the prompt") ─
-
-/** Once before any task. AI idea: log counts, or throw if CI env var is missing. */
-export async function beforeRun(_context: RunContext, _vm: HookVM): Promise<RunContext | void> {
-  return;
-}
-
-/** After all tasks in this run. AI idea: post a summary comment or call an external webhook. */
-export async function afterRun(_context: RunContext & { processed: number; skipped: number }, _vm: HookVM): Promise<void> {
-  return;
-}
-
-/** Before each code task AI run. AI idea: append coding standards or repo-specific rules to context.prompt. */
-export async function beforeEachTask(_context: TaskContext, _vm: HookVM): Promise<TaskContext | void> {
-  return;
-}
-
-/** After a code task completes the success path (push + review). */
-export async function afterEachTask(_context: TaskContext & { success: boolean }, _vm: HookVM): Promise<void> {
-  return;
-}
-
-/** Before AI-driven merge conflict resolution. AI idea: tighten context.prompt for your stack. */
-export async function beforeResolveConflicts(_context: ResolveConflictsContext, _vm: HookVM): Promise<ResolveConflictsContext | void> {
-  return;
-}
-
-/** After conflict resolution; context.resolved is false when all runners failed. */
-export async function afterResolveConflicts(_context: ResolveConflictsContext & { resolved: boolean }, _vm: HookVM): Promise<void> {
-  return;
-}
-
-/** Before non-code task AI run. AI idea: format context.prompt for ticket-style replies. */
-export async function beforeNonCodeTask(_context: NonCodeTaskContext, _vm: HookVM): Promise<NonCodeTaskContext | void> {
-  return;
-}
-
-/** After non-code task; context.output is the agent response text posted to the ticket. */
-export async function afterNonCodeTask(_context: NonCodeTaskContext & { success: boolean; output: string }, _vm: HookVM): Promise<void> {
-  return;
-}
-
-/** After the plan exists, before subtasks run. AI idea: rewrite subtask descriptions for clarity. */
-export async function beforeThinkingTask(_context: ThinkingTaskContext, _vm: HookVM): Promise<ThinkingTaskContext | void> {
-  return;
-}
-
-/** After all thinking-task subtasks complete. AI idea: notify or archive artifacts. */
-export async function afterThinkingTask(_context: ThinkingTaskContext & { success: boolean }, _vm: HookVM): Promise<void> {
-  return;
-}
+const HOOKS_BOILERPLATE = `// aidev hooks — customize the AI task automation pipeline
+//
+// Each export below is an async (context, vm) hook. Return a new/updated context object to
+// change prompts, subtasks, etc.; return nothing to keep the incoming context. Throw to abort
+// the current step (whole run, single task, conflict resolution, etc., depending on the hook).
+//
+// vm: run AI (first available agent), postComment, updateStatus, getComments, log.info/warn/error
+//
+// .ts files are loaded via jiti — no TypeScript compiler or toolchain needed.
+
+// ─── Context types (mirror aidev's internal shapes — tweak here for editor hints) ─
+
+interface RunContext {
+  config: Record<string, unknown>;
+  filter: string;
+  taskCount: number;
+}
+
+interface TaskContext {
+  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
+  config: Record<string, unknown>;
+  branchName: string;
+  prompt: string;
+}
+
+interface ResolveConflictsContext {
+  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
+  config: Record<string, unknown>;
+  branchName: string;
+  conflictFiles: string[];
+  prompt: string;
+}
+
+interface NonCodeTaskContext {
+  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
+  config: Record<string, unknown>;
+  prompt: string;
+}
+
+interface ThinkingTaskContext {
+  task: { id: string; name: string; description: string; status: string; url: string; tags: string[] };
+  config: Record<string, unknown>;
+  branchName: string;
+  subtasks: Array<{ id: number; title: string; description: string; status: string }>;
+}
+
+interface HookVM {
+  runAI(prompt: string): Promise<{ success: boolean; output: string; error: string }>;
+  postComment(taskId: string, text: string): Promise<void>;
+  updateStatus(taskId: string, status: string): Promise<void>;
+  getComments(taskId: string): Promise<Array<{ id: string; text: string; author: string }>>;
+  log: { info(msg: string): void; warn(msg: string): void; error(msg: string): void };
+}
+
+// ─── Hooks (fill in — ask an AI: "implement beforeEachTask to append X to the prompt") ─
+
+/** Once before any task. AI idea: log counts, or throw if CI env var is missing. */
+export async function beforeRun(_context: RunContext, _vm: HookVM): Promise<RunContext | void> {
+  return;
+}
+
+/** After all tasks in this run. AI idea: post a summary comment or call an external webhook. */
+export async function afterRun(_context: RunContext & { processed: number; skipped: number }, _vm: HookVM): Promise<void> {
+  return;
+}
+
+/** Before each code task AI run. AI idea: append coding standards or repo-specific rules to context.prompt. */
+export async function beforeEachTask(_context: TaskContext, _vm: HookVM): Promise<TaskContext | void> {
+  return;
+}
+
+/** After a code task completes the success path (push + review). */
+export async function afterEachTask(_context: TaskContext & { success: boolean }, _vm: HookVM): Promise<void> {
+  return;
+}
+
+/** Before AI-driven merge conflict resolution. AI idea: tighten context.prompt for your stack. */
+export async function beforeResolveConflicts(_context: ResolveConflictsContext, _vm: HookVM): Promise<ResolveConflictsContext | void> {
+  return;
+}
+
+/** After conflict resolution; context.resolved is false when all runners failed. */
+export async function afterResolveConflicts(_context: ResolveConflictsContext & { resolved: boolean }, _vm: HookVM): Promise<void> {
+  return;
+}
+
+/** Before non-code task AI run. AI idea: format context.prompt for ticket-style replies. */
+export async function beforeNonCodeTask(_context: NonCodeTaskContext, _vm: HookVM): Promise<NonCodeTaskContext | void> {
+  return;
+}
+
+/** After non-code task; context.output is the agent response text posted to the ticket. */
+export async function afterNonCodeTask(_context: NonCodeTaskContext & { success: boolean; output: string }, _vm: HookVM): Promise<void> {
+  return;
+}
+
+/** After the plan exists, before subtasks run. AI idea: rewrite subtask descriptions for clarity. */
+export async function beforeThinkingTask(_context: ThinkingTaskContext, _vm: HookVM): Promise<ThinkingTaskContext | void> {
+  return;
+}
+
+/** After all thinking-task subtasks complete. AI idea: notify or archive artifacts. */
+export async function afterThinkingTask(_context: ThinkingTaskContext & { success: boolean }, _vm: HookVM): Promise<void> {
+  return;
+}
 `;
 function ensureHooksBoilerplate(dir = process.cwd()) {
     const aidevDir = path.join(dir, '.aidev');

package/dist/commands/run.js

@@ -403,16 +403,16 @@ async function checkNeedsClarification(task, config, provider, runners) {
         logger_1.logger.warn('No AI runner available — skipping clarification check');
         return null;
     }
-    const clarificationPrompt = `You are a senior software developer reviewing a task.
-Determine if the following task has enough information to implement without further clarification.
-
-Task name: ${task.name}
-Task description: ${task.description || '(no description)'}
-
-Respond with valid JSON only:
-{
-  "clear": true|false,
-  "question": "question to ask if not clear, or null"
+    const clarificationPrompt = `You are a senior software developer reviewing a task.
+Determine if the following task has enough information to implement without further clarification.
+
+Task name: ${task.name}
+Task description: ${task.description || '(no description)'}
+
+Respond with valid JSON only:
+{
+  "clear": true|false,
+  "question": "question to ask if not clear, or null"
 }`;
     for (const runner of availableRunners) {
         const result = await runner.run(clarificationPrompt);
@@ -440,30 +440,30 @@ Respond with valid JSON only:
     return null;
 }
 function buildConflictResolutionPrompt(task, conflictFiles, context) {
-    return `You are resolving merge conflicts in a software development task branch.
-
-The task branch has fallen behind the base branch and has merge conflicts that need to be resolved.
-
-## Task context (DO NOT break this — the task must still work after conflict resolution)
-
-Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-${context}
-
-## Merge conflicts
-
-The following files have merge conflicts with conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...):
-${conflictFiles.map((f) => `- ${f}`).join('\n')}
-
-## Instructions
-
-1. Open each conflicting file and resolve the conflict markers
-2. Keep BOTH the task's changes AND the base branch updates where possible
-3. If the base branch changed something the task also changed, prefer the task's intent but make sure it works with the new base branch code
-4. Remove all conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...)
-5. Make sure the code compiles and is consistent after resolution
+    return `You are resolving merge conflicts in a software development task branch.
+
+The task branch has fallen behind the base branch and has merge conflicts that need to be resolved.
+
+## Task context (DO NOT break this — the task must still work after conflict resolution)
+
+Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+${context}
+
+## Merge conflicts
+
+The following files have merge conflicts with conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...):
+${conflictFiles.map((f) => `- ${f}`).join('\n')}
+
+## Instructions
+
+1. Open each conflicting file and resolve the conflict markers
+2. Keep BOTH the task's changes AND the base branch updates where possible
+3. If the base branch changed something the task also changed, prefer the task's intent but make sure it works with the new base branch code
+4. Remove all conflict markers (<<<<<<< HEAD, =======, >>>>>>> ...)
+5. Make sure the code compiles and is consistent after resolution
 6. Do NOT make any changes beyond what is needed to resolve the conflicts`;
 }
 async function resolveConflictsWithAI(task, config, provider, runners, context, hooks, vm, branchName) {
@@ -731,14 +731,14 @@ async function implementTask(task, branchName, branchExists, config, provider, r
     logger_1.logger.success(`Task implemented: branch ${branchName} pushed`);
 }
 function buildImplementPrompt(task, context) {
-    return `You are implementing a software development task. Make the necessary code changes to complete the task described below.
-
-Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-${context}
-
+    return `You are implementing a software development task. Make the necessary code changes to complete the task described below.
+
+Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+${context}
+
 Please implement the required changes. Focus on correctness and follow the existing code style in the project.`;
 }
 async function analyzeAndPlan(task, context, runners) {
@@ -747,28 +747,28 @@ async function analyzeAndPlan(task, context, runners) {
         logger_1.logger.error('No AI runner available for task analysis');
         return null;
     }
-    const analysisPrompt = `You are a senior software architect breaking down a development task into smaller, sequential implementation steps.
-
-Task name: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-${context}
-
-Analyze this task and break it into smaller, independently implementable sub-tasks that should be executed sequentially. Each sub-task should be a coherent unit of work that can be committed separately.
-
-Respond with valid JSON only — no markdown fences, no extra text:
-{
-  "instructions": "Detailed implementation instructions in markdown covering the full task — architecture decisions, key files to modify, edge cases to handle, testing approach",
-  "subtasks": [
-    {
-      "id": 1,
-      "title": "Short title for the sub-task",
-      "description": "Detailed description of what to implement in this step, including specific files and functions to change"
-    }
-  ]
-}
-
+    const analysisPrompt = `You are a senior software architect breaking down a development task into smaller, sequential implementation steps.
+
+Task name: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+${context}
+
+Analyze this task and break it into smaller, independently implementable sub-tasks that should be executed sequentially. Each sub-task should be a coherent unit of work that can be committed separately.
+
+Respond with valid JSON only — no markdown fences, no extra text:
+{
+  "instructions": "Detailed implementation instructions in markdown covering the full task — architecture decisions, key files to modify, edge cases to handle, testing approach",
+  "subtasks": [
+    {
+      "id": 1,
+      "title": "Short title for the sub-task",
+      "description": "Detailed description of what to implement in this step, including specific files and functions to change"
+    }
+  ]
+}
+
 Keep sub-tasks focused: 2-6 sub-tasks is ideal. Order them by dependency (foundation first).`;
     logger_1.logger.info('Analyzing task and creating implementation plan...');
     const result = await runner.run(analysisPrompt);
@@ -820,31 +820,31 @@ async function splitFailedSubtask(parentTask, plan, failedSubtask, runners) {
     const diagnostics = failedSubtask.lastError && failedSubtask.lastError !== '__git__'
         ? failedSubtask.lastError
         : '(no diagnostics captured)';
-    const splitPrompt = `You are a senior software architect helping recover a stalled implementation step by splitting it into exactly two smaller, sequential sub-tasks.
-
-Overall task: ${parentTask.name}
-${parentTask.description ? `\nTask description:\n${parentTask.description}\n` : ''}
-## Surrounding plan
-${siblings || '(no sibling sub-tasks)'}
-
-## Failed sub-task
-ID: ${formatSubtaskId(failedSubtask.id)}
-Title: ${failedSubtask.title}
-Description: ${failedSubtask.description}
-
-## Previous failure diagnostics
-${diagnostics}
-
-Split the failed sub-task above into exactly two smaller, independently implementable sub-tasks that together achieve the original goal. Each new sub-task should be a coherent unit of work that can be committed separately, ordered by dependency (foundation first). Take the diagnostics into account so the split actually addresses what broke.
-
-Respond with valid JSON only — no markdown fences, no extra text:
-{
-  "subtasks": [
-    { "title": "Short title for the first new sub-task", "description": "Detailed description of what to implement in this step" },
-    { "title": "Short title for the second new sub-task", "description": "Detailed description of what to implement in this step" }
-  ]
-}
-
+    const splitPrompt = `You are a senior software architect helping recover a stalled implementation step by splitting it into exactly two smaller, sequential sub-tasks.
+
+Overall task: ${parentTask.name}
+${parentTask.description ? `\nTask description:\n${parentTask.description}\n` : ''}
+## Surrounding plan
+${siblings || '(no sibling sub-tasks)'}
+
+## Failed sub-task
+ID: ${formatSubtaskId(failedSubtask.id)}
+Title: ${failedSubtask.title}
+Description: ${failedSubtask.description}
+
+## Previous failure diagnostics
+${diagnostics}
+
+Split the failed sub-task above into exactly two smaller, independently implementable sub-tasks that together achieve the original goal. Each new sub-task should be a coherent unit of work that can be committed separately, ordered by dependency (foundation first). Take the diagnostics into account so the split actually addresses what broke.
+
+Respond with valid JSON only — no markdown fences, no extra text:
+{
+  "subtasks": [
+    { "title": "Short title for the first new sub-task", "description": "Detailed description of what to implement in this step" },
+    { "title": "Short title for the second new sub-task", "description": "Detailed description of what to implement in this step" }
+  ]
+}
+
 Exactly two entries — no more, no fewer.`;
     logger_1.logger.info(`Splitting failed sub-task ${formatSubtaskId(failedSubtask.id)} into two smaller steps...`);
     const result = await runner.run(splitPrompt);
@@ -899,20 +899,20 @@ async function executeSubTask(subtask, task, plan, config, runners, reviewContex
     const retrySection = previousError && previousError !== '__git__'
         ? `\n## Previous attempt failure diagnostics\nThis step failed on a previous attempt. Diagnostics below — please take them into account and avoid repeating the same failure.\n\n${previousError}\n`
         : '';
-    const prompt = `You are implementing step ${subtask.id} of a multi-step task.
-
-Overall task: ${task.name}
-${task.description ? `\nTask description:\n${task.description}` : ''}
-
-## Full implementation instructions
-${instructions}
-${reviewContext || ''}${retrySection}
-## Progress
-${completedSteps || '(no steps completed yet)'}
-
-## Current step: ${subtask.id}. ${subtask.title}
-${subtask.description}
-
+    const prompt = `You are implementing step ${subtask.id} of a multi-step task.
+
+Overall task: ${task.name}
+${task.description ? `\nTask description:\n${task.description}` : ''}
+
+## Full implementation instructions
+${instructions}
+${reviewContext || ''}${retrySection}
+## Progress
+${completedSteps || '(no steps completed yet)'}
+
+## Current step: ${subtask.id}. ${subtask.title}
+${subtask.description}
+
 Implement ONLY this step. Focus on correctness and follow the existing code style.`;
     let implemented = false;
     let previousNotes = '';
@@ -1199,29 +1199,29 @@ function buildCompletionComment(branch, prUrl, config) {
 function buildNonCodePrompt(task, context) {
     const hasComments = context.trim().length > 0;
     if (hasComments) {
-        return `Task: ${task.name}
-
-Original description:
-${task.description || '(no description provided)'}
-${context}
-
-⚠️ CRITICAL: This is a FOLLOW-UP request. The conversation above contains new comments from the user.
-YOUR PRIMARY TASK is to address the LATEST comment at the bottom of the conversation - this is the user's current request.
-The latest comment may:
-- Ask for something completely different from the original task
-- Request modifications to what was already done
-- Add new requirements
-
-DO NOT repeat what was already done. DO NOT re-execute the original task unless explicitly asked.
-Focus ENTIRELY on addressing the latest comment as your main instruction.
-
+        return `Task: ${task.name}
+
+Original description:
+${task.description || '(no description provided)'}
+${context}
+
+⚠️ CRITICAL: This is a FOLLOW-UP request. The conversation above contains new comments from the user.
+YOUR PRIMARY TASK is to address the LATEST comment at the bottom of the conversation - this is the user's current request.
+The latest comment may:
+- Ask for something completely different from the original task
+- Request modifications to what was already done
+- Add new requirements
+
+DO NOT repeat what was already done. DO NOT re-execute the original task unless explicitly asked.
+Focus ENTIRELY on addressing the latest comment as your main instruction.
+
 Please provide a clear, detailed response to the LATEST comment. Your response will be posted as a comment on the task ticket, so write it as a direct answer or explanation addressed to the person who wrote the latest comment.`;
     }
-    return `Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-
+    return `Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+
 Please provide a clear, detailed response to this task. Your response will be posted as a comment on the task ticket, so write it as a direct answer or explanation addressed to the person who created the task.`;
 }
 function buildNonCodeCompletionComment(config, agentResponse) {
@@ -1531,22 +1531,22 @@ async function implementReviewTask(task, branchName, config, provider, runners,
     logger_1.logger.success(`Review comments addressed for: ${task.name}`);
 }
 function buildReviewPrompt(task, threads) {
-    let prompt = `You are addressing code review comments on a pull request for a software development task.
-
-Task: ${task.name}
-
-Description:
-${task.description || '(no description provided)'}
-
-## Unresolved Code Review Threads
-
-The following review threads need to be addressed. For each thread, either:
-- Fix the code as requested (make the changes directly in the files)
-- Or, if it's a discussion/question that doesn't require code changes, output a REPLY block:
-  <!-- AIDEV-REPLY thread_id -->Your reply here<!-- /AIDEV-REPLY -->
-
-Replace "thread_id" with the actual thread ID shown below.
-
+    let prompt = `You are addressing code review comments on a pull request for a software development task.
+
+Task: ${task.name}
+
+Description:
+${task.description || '(no description provided)'}
+
+## Unresolved Code Review Threads
+
+The following review threads need to be addressed. For each thread, either:
+- Fix the code as requested (make the changes directly in the files)
+- Or, if it's a discussion/question that doesn't require code changes, output a REPLY block:
+  <!-- AIDEV-REPLY thread_id -->Your reply here<!-- /AIDEV-REPLY -->
+
+Replace "thread_id" with the actual thread ID shown below.
+
 `;
     for (const thread of threads) {
         const location = thread.line
@@ -1558,12 +1558,12 @@ Replace "thread_id" with the actual thread ID shown below.
         }
         prompt += '\n';
     }
-    prompt += `## Instructions
-
-1. Read each review thread carefully
-2. For code change requests: make the fix directly in the relevant file(s)
-3. For questions or discussions: output a REPLY block with a clear, helpful response
-4. You may handle multiple threads — some with code fixes, others with replies
+    prompt += `## Instructions
+
+1. Read each review thread carefully
+2. For code change requests: make the fix directly in the relevant file(s)
+3. For questions or discussions: output a REPLY block with a clear, helpful response
+4. You may handle multiple threads — some with code fixes, others with replies
 5. Focus on correctness and follow the existing code style`;
     return prompt;
 }

package/dist/github.js

@@ -86,25 +86,25 @@ function getPrNumberForBranch(branch) {
     }
 }
 function fetchUnresolvedReviewThreads(owner, repo, prNumber) {
-    const query = `query($owner: String!, $repo: String!, $prNumber: Int!) {
-    repository(owner: $owner, name: $repo) {
-      pullRequest(number: $prNumber) {
-        reviewThreads(first: 100) {
-          nodes {
-            id
-            isResolved
-            path
-            line
-            comments(first: 50) {
-              nodes {
-                body
-                author { login }
-              }
-            }
-          }
-        }
-      }
-    }
+    const query = `query($owner: String!, $repo: String!, $prNumber: Int!) {
+    repository(owner: $owner, name: $repo) {
+      pullRequest(number: $prNumber) {
+        reviewThreads(first: 100) {
+          nodes {
+            id
+            isResolved
+            path
+            line
+            comments(first: 50) {
+              nodes {
+                body
+                author { login }
+              }
+            }
+          }
+        }
+      }
+    }
   }`;
     const result = gh([
         'api', 'graphql',
@@ -173,10 +173,10 @@ function mergePullRequest(branch) {
     return { success: true, error: '' };
 }
 function replyToReviewThread(threadId, body) {
-    const mutation = `mutation($threadId: ID!, $body: String!) {
-    addPullRequestReviewThreadReply(input: { pullRequestReviewThreadId: $threadId, body: $body }) {
-      comment { id }
-    }
+    const mutation = `mutation($threadId: ID!, $body: String!) {
+    addPullRequestReviewThreadReply(input: { pullRequestReviewThreadId: $threadId, body: $body }) {
+      comment { id }
+    }
   }`;
     const result = gh([
         'api', 'graphql',
@@ -199,10 +199,10 @@ function filterUnresolvedByNonAidev(threads, commentPrefix) {
     });
 }
 function resolveReviewThread(threadId) {
-    const mutation = `mutation($threadId: ID!) {
-    resolveReviewThread(input: { threadId: $threadId }) {
-      thread { isResolved }
-    }
+    const mutation = `mutation($threadId: ID!) {
+    resolveReviewThread(input: { threadId: $threadId }) {
+      thread { isResolved }
+    }
   }`;
     const result = gh([
         'api', 'graphql',