feat: add deterministic Ghost check JSON report#204
Draft
chailandau wants to merge 1 commit into
Draft
Conversation
2fb6da7 to
9cb901a
Compare
Co-authored-by: Goose <opensource@block.xyz> Ai-assisted: true
9cb901a to
12932b8
Compare
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.
Why
Enterprise review systems need a deterministic Ghost JSON contract they can run in CI or a first-party review bot, then map into their existing PR comment and status workflows without Ghost owning GitHub posting identity.
What
ghost checkfor detector-backedghost.check/v1markdown checks.ghost.check-report/v1JSON with path/line findings for review orchestrators.forbidden-regexandrequired-regexdetectors over unified diff additions.detector:in the existing agent-evaluatedghost checkslane.Validation
pnpm buildpnpm checkpnpm testGenerated with Goose