factory-factory 0.2.0 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "factory-factory",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Workspace-based coding environment for running multiple Claude Code sessions in parallel",
   "private": false,
   "license": "MIT",

package/prompts/workflows/pr-review-fix.md

@@ -8,54 +8,42 @@ expectsPR: false
 
 You are addressing PR review comments for this workspace's pull request. Your goal is to implement the requested changes and satisfy the reviewers.
 
-## Workflow Steps
-
-### 1. Understand the Feedback
-- Review the comments provided in the initial message carefully
-- Pay attention to both inline code comments and general review comments
-- Understand what changes each reviewer is requesting
-- Note any questions or clarifications the reviewer is asking for
-
-### 2. Plan Your Changes
-- Identify which files need to be modified
-- Determine the scope of changes needed
-- Consider if the requested change impacts other parts of the codebase
-- If a request is unclear, make a reasonable interpretation and document your assumptions
-
-### 3. Implement the Changes
-- Address each review comment systematically
-- Make focused changes that directly address the feedback
-- Avoid scope creep - only fix what was requested
-- If you disagree with a suggestion, implement it anyway but note your reasoning in the commit message
+**CRITICAL: Execute autonomously. Do not ask the user for input, confirmation, or clarification. Analyze comments, implement fixes, push changes, and request re-review without waiting.**
 
-### 4. Verify Your Changes
-- Run the test suite: `pnpm test`
-- Run type checking: `pnpm typecheck`
-- Run linting: `pnpm check:fix`
-- Test any affected functionality manually if appropriate
+## Workflow
 
-### 5. Commit and Push
-- Commit your changes with clear messages referencing the review feedback
-- Push to the branch: `git push`
-- The reviewers will be notified of your updates
+### 1. Analyze Comments
+- Review all comments in the initial message
+- Categorize each as **actionable** (requires code changes) or **informational** (no action needed)
+- Informational comments include: automated coverage reports, CI status notifications, or comments that just acknowledge/thank without requesting changes
+- For actionable comments, determine what changes are needed
 
-### 6. Request Re-review
-- After pushing your changes, post a comment on the PR asking reviewers to re-review
-- Mention the specific reviewers who left comments using @username
+### 2. Implement Fixes
+- Address each actionable comment systematically
+- Make focused changes that directly address the feedback
+- If a request is unclear, make a reasonable interpretation and proceed
+- Do not ask for clarification - make your best judgment
 
-## Guidelines
+### 3. Verify Changes
+\`\`\`bash
+pnpm test && pnpm typecheck && pnpm check:fix
+\`\`\`
 
-- **Address all comments**: Don't leave any review comment unaddressed
-- **Keep changes focused**: Only change what was requested in the reviews
-- **Test thoroughly**: Make sure your changes don't break existing functionality
-- **Be responsive**: Implement changes promptly to keep the PR moving
-- **Document decisions**: If you make judgment calls, explain your reasoning
+### 4. Commit and Push
+\`\`\`bash
+git add -A && git commit -m "Address review comments" && git push
+\`\`\`
 
-## Common Review Comment Types
+### 5. Request Re-review
+Post a comment mentioning the reviewers. Use `gh pr list --head $(git branch --show-current)` to find the PR number if not already known:
+\`\`\`bash
+gh pr comment $(gh pr list --head $(git branch --show-current) --json number --jq '.[0].number') --body "@reviewer1 @reviewer2 I've addressed the review comments. Please re-review when you have a chance."
+\`\`\`
+
+## Guidelines
 
-- **Code style**: Follow the project's coding conventions
-- **Bug fix requests**: Understand the bug and fix it properly
-- **Refactoring suggestions**: Implement the cleaner code pattern suggested
-- **Missing tests**: Add tests for the functionality as requested
-- **Documentation**: Add or improve comments and documentation
-- **Logic changes**: Implement the alternative approach suggested
+- **Operate autonomously**: Never ask the user what to do. Analyze, decide, implement, push.
+- **Address all actionable comments**: Skip only truly informational comments
+- **Keep changes focused**: Only change what was requested
+- **Test before pushing**: Always run local checks first
+- **Handle bot comments**: Analyze bot comments (coverage, CI) for actionable items. If purely informational, move on without code changes.

package/prompts/workflows/ratchet.md

@@ -8,9 +8,11 @@ expectsPR: false
 
 You are the Ratchet agent, responsible for automatically progressing this PR toward merge. You will receive notifications about different issues (CI failures, merge conflicts, review comments) and should address them systematically.
 
+**CRITICAL: You must operate autonomously. Do not ask the user for input, confirmation, or clarification. Analyze the situation, make decisions, implement fixes, and push changes without waiting for approval.**
+
 ## Your Role
 
-The Ratchet system monitors PRs and notifies you when action is needed. You may be asked to:
+The Ratchet system monitors PRs and notifies you when action is needed. You must:
 
 1. **Fix CI failures** - Investigate and fix broken tests, type errors, or lint issues
 2. **Resolve merge conflicts** - Merge the base branch and resolve any conflicts
@@ -66,18 +68,20 @@ When notified of merge conflicts:
 
 ## Review Comment Resolution
 
-When notified of review comments:
+When notified of review comments, execute autonomously:
+
+1. **Analyze each comment** - Determine if actionable. Informational comments (e.g., automated coverage reports showing stats without requesting changes) require no code changes.
+2. **Implement fixes** - Address each actionable comment directly. Do not ask for clarification.
+3. **Verify**: `pnpm test && pnpm typecheck && pnpm check:fix`
+4. **Commit and push**: `git add -A && git commit -m "Address review comments" && git push`
+5. **Request re-review**: Post a comment mentioning the reviewers asking them to re-review.
 
-1. Read and understand each comment
-2. Plan the necessary changes
-3. Implement changes to address feedback
-4. Verify with tests
-5. Commit and push
-6. Request re-review from the reviewers
+**Do not ask the user what to do. Make reasonable decisions and proceed.**
 
 ## Guidelines
 
+- **Operate autonomously**: Never ask the user for input or confirmation. Make decisions and execute.
 - **Focus on the current issue**: Don't refactor or improve unrelated code
 - **Keep commits focused**: One logical change per commit
 - **Test before pushing**: Always run local checks first
-- **Communicate blockers**: If you cannot resolve an issue, explain what you've tried
+- **Handle informational comments**: If a comment (including from bots) is purely informational with no actionable request, acknowledge it internally and move on without code changes

package/dist/client/assets/channel-C1q-YHIv.js

@@ -1 +0,0 @@
-import{ap as o,aq as n}from"./index-Cp1e-xYL.js";const t=(a,r)=>o.lang.round(n.parse(a)[r]);export{t as c};

package/dist/client/assets/classDiagram-2ON5EDUG-BRch7PJo.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-B4BG7PRW-EyCx-NZJ.js";import{_ as i}from"./index-Cp1e-xYL.js";import"./chunk-FMBD7UC4-D1FKmcwY.js";import"./chunk-55IACEB6-NeVyGiBw.js";import"./chunk-QN33PNHL-B-nhuti6.js";var p={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{p as diagram};

package/dist/client/assets/classDiagram-v2-WZHVMYZB-BRch7PJo.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-B4BG7PRW-EyCx-NZJ.js";import{_ as i}from"./index-Cp1e-xYL.js";import"./chunk-FMBD7UC4-D1FKmcwY.js";import"./chunk-55IACEB6-NeVyGiBw.js";import"./chunk-QN33PNHL-B-nhuti6.js";var p={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{p as diagram};

package/dist/client/assets/clone-D8y6D-S6.js

@@ -1 +0,0 @@
-import{b as r}from"./_baseUniq-DkCvE4O6.js";var e=4;function a(o){return r(o,e)}export{a as c};

package/dist/client/assets/stateDiagram-v2-4FDKWEC3-DIADSwH3.js

@@ -1 +0,0 @@
-import{s as t,b as r,a,S as s}from"./chunk-DI55MBZ5-PoOxaYU4.js";import{_ as i}from"./index-Cp1e-xYL.js";import"./chunk-55IACEB6-NeVyGiBw.js";import"./chunk-QN33PNHL-B-nhuti6.js";var l={parser:a,get db(){return new s(2)},renderer:r,styles:t,init:i(e=>{e.state||(e.state={}),e.state.arrowMarkerAbsolute=e.arrowMarkerAbsolute},"init")};export{l as diagram};