Draft
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed:
CombinedOutputmixes stderr into JSON parsing- Replaced
cmd.CombinedOutput()withcmd.Output()inhooksInstalledso JSON unmarshaling only consumes stdout while still surfacing stderr on failures.
- Replaced
Or push these changes by commenting:
@cursor push cf50eb3fbf
Preview (cf50eb3fbf)
diff --git a/e2e/lifecycle_test.go b/e2e/lifecycle_test.go
--- a/e2e/lifecycle_test.go
+++ b/e2e/lifecycle_test.go
@@ -219,9 +219,12 @@
"LANG=en_US.UTF-8",
)
- out, err := cmd.CombinedOutput()
+ out, err := cmd.Output()
if err != nil {
- t.Fatalf("%s are-hooks-installed failed: %v\n%s", binPath, err, out)
+ if exitErr, ok := err.(*exec.ExitError); ok {
+ t.Fatalf("%s are-hooks-installed failed: %v\nstdout: %s\nstderr: %s", binPath, err, out, exitErr.Stderr)
+ }
+ t.Fatalf("%s are-hooks-installed failed: %v\nstdout: %s", binPath, err, out)
}
var resp struct {This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Note
Medium Risk
Moderate risk because it changes CI and local test execution paths (removing protocol-level
e2etests and adjustingMakefiletargets), which could hide regressions if the new compliance workflow or lifecycle filtering is misconfigured.Overview
Shifts the external-agent testing model to black-box-first: protocol compliance is now validated via the shared
external-agents-testssuite (and new.github/workflows/protocol-compliance.yml), while this repo’se2e/harness is explicitly narrowed to lifecycle integration scenarios.Removes the repo-local protocol/subcommand test harness code (
e2e/harness.go,e2e/testenv.go, fixtures, and the Kiro protocol test package) and updates lifecycle coverage to directly executeare-hooks-installedwhen asserting hook installation.Updates the external-agent builder skill docs (
SKILL.md,write-tests.md,implement.md), top-level docs (README.md,AGENTS.md,e2e/README.md), and theMakefileto reflect the new split and to run lifecycle tests by default (with optionalAGENTfiltering).Written by Cursor Bugbot for commit 1fdb39c. Configure here.