reviewloop 0.3.3__tar.gz → 0.3.4__tar.gz

{reviewloop-0.3.3 → reviewloop-0.3.4}/.claude/skills/reviewloop/SKILL.md

@@ -10,9 +10,20 @@ allowed-tools:
 
 ## Autonomous Review Loop
 
+**CRITICAL: Never merge a PR unless the user explicitly asks you to.**
+
 This is an automated review loop. Follow these steps:
 
-### 1. Wait for CI to complete
+### 1. Prepare branch and PR
+
+Before starting the review cycle, ensure all changes are committed, pushed, and a PR exists.
+
+1. Verify you are NOT on the default branch. If on the default branch, inform the user and stop.
+2. If there are uncommitted changes (staged or unstaged), commit them with a descriptive message. Skip if the working directory is clean.
+3. Push commits to the remote. If no upstream tracking branch exists, push with the `-u` flag. Skip if already up-to-date.
+4. Check if a PR exists for the current branch (`gh pr view`). If none exists, create one with `gh pr create --fill`.
+
+### 2. Wait for CI to complete
 
 Run `.claude/skills/reviewloop/scripts/review-wait.sh` to poll for CI completion.
 
@@ -21,7 +32,7 @@ Run `.claude/skills/reviewloop/scripts/review-wait.sh` to poll for CI completion
 - Times out after 10 minutes (configurable with `--timeout=SECONDS`)
 - Exits immediately if no CI is in progress
 
-### 2. Fetch and address comments
+### 3. Fetch and address comments
 
 Once CI completes:
 
@@ -32,14 +43,18 @@ Once CI completes:
 5. For inline threads: resolve via the `gh api graphql` mutation shown in the file (whether addressed or rejected)
 6. For general review comments: react with thumbs-up via the mutation shown in the file to mark as processed (even if no action was needed)
 
-### 3. Verify and commit
+### 4. Verify and commit
 
 1. Run `.claude/skills/reviewloop/scripts/review-comments.sh` again to verify no unresolved comments remain
 2. Run your project's linting and type-checking commands to ensure code quality
 3. Commit and push changes
 
-### 4. Loop
+### 5. Loop
+
+Go back to step 2 - wait for the next review triggered by the push.
 
-Go back to step 1 - wait for the next review triggered by the push.
+**Exit condition**: When `.claude/skills/reviewloop/scripts/review-comments.sh` shows no comments, provide a summary with:
 
-**Exit condition**: When `.claude/skills/reviewloop/scripts/review-comments.sh` shows no comments. Give a brief high-level summary of what was addressed.
+1. **PR link**: The full clickable URL of the PR (from step 1 or via `gh pr view --json url -q '.url'`)
+2. **Overall PR summary**: A brief high-level summary of what the PR accomplishes overall
+3. **Review loop changes**: A summary of what was specifically changed during the review loop to address reviewer comments. If no changes were made during the review loop, state that no changes were needed.

{reviewloop-0.3.3 → reviewloop-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: reviewloop
-Version: 0.3.3
+Version: 0.3.4
 Summary: Autonomous review loop - automates the review-fix-push cycle
 Project-URL: Homepage, https://github.com/fabianboth/autonomous-review-loop
 Project-URL: Repository, https://github.com/fabianboth/autonomous-review-loop.git

{reviewloop-0.3.3 → reviewloop-0.3.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "reviewloop"
-version = "0.3.3"
+version = "0.3.4"
 description = "Autonomous review loop - automates the review-fix-push cycle"
 readme = "README_PYPI.md"
 license = "MIT"

{reviewloop-0.3.3 → reviewloop-0.3.4}/src/reviewloop_cli/templates/SKILL.md

@@ -10,9 +10,20 @@ allowed-tools:
 
 ## Autonomous Review Loop
 
+**CRITICAL: Never merge a PR unless the user explicitly asks you to.**
+
 This is an automated review loop. Follow these steps:
 
-### 1. Wait for CI to complete
+### 1. Prepare branch and PR
+
+Before starting the review cycle, ensure all changes are committed, pushed, and a PR exists.
+
+1. Verify you are NOT on the default branch. If on the default branch, inform the user and stop.
+2. If there are uncommitted changes (staged or unstaged), commit them with a descriptive message. Skip if the working directory is clean.
+3. Push commits to the remote. If no upstream tracking branch exists, push with the `-u` flag. Skip if already up-to-date.
+4. Check if a PR exists for the current branch (`gh pr view`). If none exists, create one with `gh pr create --fill`.
+
+### 2. Wait for CI to complete
 
 Run `.claude/skills/reviewloop/scripts/review-wait.sh` to poll for CI completion.
 
@@ -21,7 +32,7 @@ Run `.claude/skills/reviewloop/scripts/review-wait.sh` to poll for CI completion
 - Times out after 10 minutes (configurable with `--timeout=SECONDS`)
 - Exits immediately if no CI is in progress
 
-### 2. Fetch and address comments
+### 3. Fetch and address comments
 
 Once CI completes:
 
@@ -32,14 +43,18 @@ Once CI completes:
 5. For inline threads: resolve via the `gh api graphql` mutation shown in the file (whether addressed or rejected)
 6. For general review comments: react with thumbs-up via the mutation shown in the file to mark as processed (even if no action was needed)
 
-### 3. Verify and commit
+### 4. Verify and commit
 
 1. Run `.claude/skills/reviewloop/scripts/review-comments.sh` again to verify no unresolved comments remain
 2. Run your project's linting and type-checking commands to ensure code quality
 3. Commit and push changes
 
-### 4. Loop
+### 5. Loop
+
+Go back to step 2 - wait for the next review triggered by the push.
 
-Go back to step 1 - wait for the next review triggered by the push.
+**Exit condition**: When `.claude/skills/reviewloop/scripts/review-comments.sh` shows no comments, provide a summary with:
 
-**Exit condition**: When `.claude/skills/reviewloop/scripts/review-comments.sh` shows no comments. Give a brief high-level summary of what was addressed.
+1. **PR link**: The full clickable URL of the PR (from step 1 or via `gh pr view --json url -q '.url'`)
+2. **Overall PR summary**: A brief high-level summary of what the PR accomplishes overall
+3. **Review loop changes**: A summary of what was specifically changed during the review loop to address reviewer comments. If no changes were made during the review loop, state that no changes were needed.

{reviewloop-0.3.3 → reviewloop-0.3.4}/uv.lock

@@ -86,7 +86,7 @@ wheels = [
 
 [[package]]
 name = "reviewloop"
-version = "0.3.2"
+version = "0.3.4"
 source = { editable = "." }
 dependencies = [
     { name = "readchar" },