Add contribution readiness - #11
Merged
Merged
Conversation
N0zoM1z0
force-pushed
the
agent/contribution-readiness
branch
from
July 17, 2026 16:22
90ea856 to
03b124e
Compare
Collaborator
Author
|
LGTM! |
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.
Summary
readiness opportunitygate with deterministic pass/warn/block/unknown rule output.readiness explainfor per-check details, evidence references, and remediation.Why
This gives contributors and agents a final local submit-readiness check before preparing public issue or PR drafts. It surfaces stale evidence, unresolved contradictions, target-thread state, validation state, and collision signals without network access, process execution, or corpus mutation.
Validation
git diff --checkGOMAXPROCS=2 go test -p=2 -count=1 ./internal/app ./internal/cli ./internal/corpusGOMAXPROCS=2 go test -p=2 -count=1 ./...Note:
golangci-lintis not installed in this local environment, so linter validation is left to CI.