lalph 0.3.55 → 0.3.56

package/dist/cli.mjs

@@ -233026,24 +233026,18 @@ If for any reason you get stuck on a task, mark the task back as "todo" by updat
 challenges faced.
 
 ${taskGuidelines(options)}`;
-	const prompt = (options) => `# The task
+	const prompt = (options) => `# ${options.task.title}
 
-ID: ${options.task.id}
-Task: ${options.task.title}
-Description:
+Task ID: ${options.task.id}
 
 ${options.task.description}
 
-# Instructions
+### Instructions
 
-Your job is to implement the task described above.
+Your job is to implement the task described above.${options.task.description.includes(options.specsDirectory) ? `\nMake sure to review the prd.yml for any key information that may help you with this task.` : ""}
 
-1. Carefully study the prd.yml file to understand the context of the task, and
-   discover any key learnings from previous work.
-   Also read the ${options.specsDirectory}/README.md file (if available), to see
-   if any previous specifications could assist you.
-2. ${options.gitFlow.setupInstructions(options)}
-3. Implement the task.
+1. ${options.gitFlow.setupInstructions(options)}
+2. Implement the task.
    - If this task is a research task, **do not** make any code changes yet.
    - If this task is a research task and you add follow-up tasks, include (at least) "${options.task.id}" in the new task's \`blockedBy\` field.
    - **If at any point** you discover something that needs fixing, or another task
@@ -233051,15 +233045,14 @@ Your job is to implement the task described above.
      you plan to fix it as part of this task.
    - Add important discoveries about the codebase, or challenges faced to the task's
      \`description\`. More details below.
-4. Run any checks / feedback loops, such as type checks, unit tests, or linting.
-5. ${options.gitFlow.commitInstructions({
+3. Run any checks / feedback loops, such as type checks, unit tests, or linting.
+4. ${options.gitFlow.commitInstructions({
 		githubPrInstructions: sourceMeta.githubPrInstructions,
 		githubPrNumber: options.githubPrNumber,
 		taskId: options.task.id ?? "unknown",
 		targetBranch: options.targetBranch
 	})}
-6. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}**
-   your changes, update the prd.yml to reflect any changes in the task state.
+5. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}** your changes, update the prd.yml to reflect any changes in the task state.
    - Rewrite the notes in the description to include only the key discoveries and information that could speed up future work on other tasks. Make sure to preserve important information such as specification file references.
    - If you believe the task is complete, update the \`state\` to "in-review".
 
@@ -233070,16 +233063,12 @@ Task ID: ${options.task.id}
 
 ${options.task.description}
 
-# Workflow
+### Instructions
 
-All steps must be done before the task can be considered complete.
+All steps must be done before the task can be considered complete.${options.task.description.includes(options.specsDirectory) ? `\nMake sure to review the previous tasks (using "listTasks") for any key information that may help you with this task.` : ""}
 
-1. Carefully study the current task list to understand the context of the task, and
-   discover any key learnings from previous work.
-   Also read the ${options.specsDirectory}/README.md file (if available), to see
-   if any previous specifications could assist you.
-2. ${options.gitFlow.setupInstructions(options)}
-3. Implement the task.
+1. ${options.gitFlow.setupInstructions(options)}
+2. Implement the task.
    - If this task is a research task, **do not** make any code changes yet.
    - If this task is a research task and you add follow-up tasks, include (at least) "${options.task.id}" in the new task's \`blockedBy\` field.
    - **If at any point** you discover something that needs fixing, or another task
@@ -233087,15 +233076,14 @@ All steps must be done before the task can be considered complete.
      as part of this task.
    - Add important discoveries about the codebase, or challenges faced to the task's
      \`description\`. More details below.
-4. Run any checks / feedback loops, such as type checks, unit tests, or linting.
-5. ${options.gitFlow.commitInstructions({
+3. Run any checks / feedback loops, such as type checks, unit tests, or linting.
+4. ${options.gitFlow.commitInstructions({
 		githubPrInstructions: sourceMeta.githubPrInstructions,
 		githubPrNumber: options.githubPrNumber,
 		taskId: options.task.id ?? "unknown",
 		targetBranch: options.targetBranch
 	})}
-6. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}**
-   your changes, update current task to reflect any changes in the task state.
+5. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}** your changes, update current task to reflect any changes in the task state.
    - Rewrite the notes in the description to include only the key discoveries and information that could speed up future work on other tasks. Make sure to preserve important information such as specification file references.
    - If you believe the task is complete, update the \`state\` to "in-review".`;
 	const promptReview = (options) => `A previous engineer has completed a task from the instructions below.
@@ -233919,7 +233907,7 @@ const GitFlowPR = succeed$4(GitFlow, GitFlow.of({
 	requiresGithubPr: true,
 	branch: void 0,
 	setupInstructions: ({ githubPrNumber }) => githubPrNumber ? `The Github PR #${githubPrNumber} has been detected for this task and the branch has been checked out.
-   - **REVIEW FEEDBACK** in the .lalph/feedback.md file.` : `Create a new branch for the task using the format \`{task id}/description\`, using the current HEAD as the base (don't checkout any other branches first).`,
+   - **REVIEW ALL FEEDBACK** in the .lalph/feedback.md file.` : `You are currently on a new branch for this task. You do not need to checkout any other branches.`,
 	commitInstructions: (options) => `${!options.githubPrNumber ? `Create a pull request for this task. If the target branch does not exist, create it first.` : "Commit and push your changes to the pull request."}
    ${options.githubPrInstructions}
    The PR description should include a summary of the changes made.${options.targetBranch ? `\n   - The target branch for the PR should be \`${options.targetBranch}\`.` : ""}
@@ -234186,6 +234174,10 @@ const run = fnUntraced(function* (options) {
 		yield* worktree.exec`gh pr checkout ${chosenTask.githubPrNumber}`;
 		const feedback = yield* gh.prFeedbackMd(chosenTask.githubPrNumber);
 		yield* fs.writeFileString(pathService.join(worktree.directory, ".lalph", "feedback.md"), feedback);
+	} else if (gitFlow.requiresGithubPr) {
+		const branchName = `lalph/${taskId.replace(/#/g, "").replace(/[^a-zA-Z0-9-_]/g, "-")}`;
+		yield* worktree.exec`git branch -D ${branchName}`;
+		yield* worktree.exec`git checkout -b ${branchName}`;
 	}
 	const taskPreset = getOrElse$2(yield* source.issueCliAgentPreset(chosenTask.prd), () => preset);
 	const catchStallInReview = (effect) => catchIf$2(effect, (u) => u instanceof RunnerStalled, fnUntraced(function* (e) {
@@ -234628,7 +234620,7 @@ const commandEdit = make$46("edit").pipe(withDescription("Open the selected proj
 const commandSource = make$46("source").pipe(withDescription("Select the issue source to use (e.g. GitHub Issues or Linear). This applies to all projects."), withHandler(() => selectIssueSource), provide(Settings.layer));
 //#endregion
 //#region package.json
-var version = "0.3.55";
+var version = "0.3.56";
 //#endregion
 //#region src/commands/projects/ls.ts
 const commandProjectsLs = make$46("ls").pipe(withDescription("List configured projects and how they run (enabled state, concurrency, branch, git flow, review agent)."), withHandler(fnUntraced(function* () {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "lalph",
   "type": "module",
-  "version": "0.3.55",
+  "version": "0.3.56",
   "publishConfig": {
     "access": "public"
   },

package/src/GitFlow.ts

@@ -61,8 +61,8 @@ export const GitFlowPR = Layer.succeed(
     setupInstructions: ({ githubPrNumber }) =>
       githubPrNumber
         ? `The Github PR #${githubPrNumber} has been detected for this task and the branch has been checked out.
-   - **REVIEW FEEDBACK** in the .lalph/feedback.md file.`
-        : `Create a new branch for the task using the format \`{task id}/description\`, using the current HEAD as the base (don't checkout any other branches first).`,
+   - **REVIEW ALL FEEDBACK** in the .lalph/feedback.md file.`
+        : `You are currently on a new branch for this task. You do not need to checkout any other branches.`,
 
     commitInstructions: (
       options,

package/src/PromptGen.ts

@@ -178,24 +178,22 @@ ${taskGuidelines(options)}`
         readonly specsDirectory: string
         readonly githubPrNumber: number | undefined
         readonly gitFlow: GitFlow["Service"]
-      }) => `# The task
+      }) => `# ${options.task.title}
 
-ID: ${options.task.id}
-Task: ${options.task.title}
-Description:
+Task ID: ${options.task.id}
 
 ${options.task.description}
 
-# Instructions
+### Instructions
 
-Your job is to implement the task described above.
+Your job is to implement the task described above.${
+        options.task.description.includes(options.specsDirectory)
+          ? `\nMake sure to review the prd.yml for any key information that may help you with this task.`
+          : ""
+      }
 
-1. Carefully study the prd.yml file to understand the context of the task, and
-   discover any key learnings from previous work.
-   Also read the ${options.specsDirectory}/README.md file (if available), to see
-   if any previous specifications could assist you.
-2. ${options.gitFlow.setupInstructions(options)}
-3. Implement the task.
+1. ${options.gitFlow.setupInstructions(options)}
+2. Implement the task.
    - If this task is a research task, **do not** make any code changes yet.
    - If this task is a research task and you add follow-up tasks, include (at least) "${options.task.id}" in the new task's \`blockedBy\` field.
    - **If at any point** you discover something that needs fixing, or another task
@@ -203,15 +201,14 @@ Your job is to implement the task described above.
      you plan to fix it as part of this task.
    - Add important discoveries about the codebase, or challenges faced to the task's
      \`description\`. More details below.
-4. Run any checks / feedback loops, such as type checks, unit tests, or linting.
-5. ${options.gitFlow.commitInstructions({
+3. Run any checks / feedback loops, such as type checks, unit tests, or linting.
+4. ${options.gitFlow.commitInstructions({
         githubPrInstructions: sourceMeta.githubPrInstructions,
         githubPrNumber: options.githubPrNumber,
         taskId: options.task.id ?? "unknown",
         targetBranch: options.targetBranch,
       })}
-6. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}**
-   your changes, update the prd.yml to reflect any changes in the task state.
+5. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}** your changes, update the prd.yml to reflect any changes in the task state.
    - Rewrite the notes in the description to include only the key discoveries and information that could speed up future work on other tasks. Make sure to preserve important information such as specification file references.
    - If you believe the task is complete, update the \`state\` to "in-review".
 
@@ -229,16 +226,16 @@ Task ID: ${options.task.id}
 
 ${options.task.description}
 
-# Workflow
+### Instructions
 
-All steps must be done before the task can be considered complete.
+All steps must be done before the task can be considered complete.${
+        options.task.description.includes(options.specsDirectory)
+          ? `\nMake sure to review the previous tasks (using "listTasks") for any key information that may help you with this task.`
+          : ""
+      }
 
-1. Carefully study the current task list to understand the context of the task, and
-   discover any key learnings from previous work.
-   Also read the ${options.specsDirectory}/README.md file (if available), to see
-   if any previous specifications could assist you.
-2. ${options.gitFlow.setupInstructions(options)}
-3. Implement the task.
+1. ${options.gitFlow.setupInstructions(options)}
+2. Implement the task.
    - If this task is a research task, **do not** make any code changes yet.
    - If this task is a research task and you add follow-up tasks, include (at least) "${options.task.id}" in the new task's \`blockedBy\` field.
    - **If at any point** you discover something that needs fixing, or another task
@@ -246,15 +243,14 @@ All steps must be done before the task can be considered complete.
      as part of this task.
    - Add important discoveries about the codebase, or challenges faced to the task's
      \`description\`. More details below.
-4. Run any checks / feedback loops, such as type checks, unit tests, or linting.
-5. ${options.gitFlow.commitInstructions({
+3. Run any checks / feedback loops, such as type checks, unit tests, or linting.
+4. ${options.gitFlow.commitInstructions({
         githubPrInstructions: sourceMeta.githubPrInstructions,
         githubPrNumber: options.githubPrNumber,
         taskId: options.task.id ?? "unknown",
         targetBranch: options.targetBranch,
       })}
-6. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}**
-   your changes, update current task to reflect any changes in the task state.
+5. **After ${options.gitFlow.requiresGithubPr ? "pushing" : "committing"}** your changes, update current task to reflect any changes in the task state.
    - Rewrite the notes in the description to include only the key discoveries and information that could speed up future work on other tasks. Make sure to preserve important information such as specification file references.
    - If you believe the task is complete, update the \`state\` to "in-review".`
 

package/src/commands/root.ts

@@ -178,6 +178,10 @@ const run = Effect.fnUntraced(
         pathService.join(worktree.directory, ".lalph", "feedback.md"),
         feedback,
       )
+    } else if (gitFlow.requiresGithubPr) {
+      const branchName = `lalph/${taskId.replace(/#/g, "").replace(/[^a-zA-Z0-9-_]/g, "-")}`
+      yield* worktree.exec`git branch -D ${branchName}`
+      yield* worktree.exec`git checkout -b ${branchName}`
     }
 
     const taskPreset = Option.getOrElse(