feat: agent-ready — installable SKILL.md skills, AGENTS.md, coding-ag… - #926
Open
bearsyankees wants to merge 6 commits into
Open
feat: agent-ready — installable SKILL.md skills, AGENTS.md, coding-ag…#926bearsyankees wants to merge 6 commits into
bearsyankees wants to merge 6 commits into
Conversation
Contributor
Greptile SummaryAdds installable agent skills and supporting documentation for running Strix, remediating findings, using the cloud API, and configuring CI.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Important Files Changed
Reviews (5): Last reviewed commit: "docs(skills): enforce scan completion in..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
- New strix-cloud-api skill: token/scopes, register assets, launch+poll scans, read findings, SARIF/report export, PR reviews, schedules, webhooks - strix-pentest: unbiased OSS-vs-Cloud decision guide; both run paths - strix-fix-findings, strix-ci-setup: cover cloud verify + managed PR reviews - AGENTS.md/README/coding-agents docs: document both run modes
- CI + verify: resolve the PR/default base branch instead of hard-coding origin/main (repos use master/develop; GitHub Actions uses github.base_ref) - Document the budget/fail-open caveat: exit 0 means clean for what was analyzed, not full coverage; size budget to complete and check run.json
Contributor
- Drop @{u} fallback that could resolve the current feature branch as its
own diff base (empty diff -> falsely clean verification)
- Prefer origin/HEAD, then a common default branch that exists, else HEAD~1
- CI: resolve base branch without pipe-masking (parameter expansion + ref
verification) so a failed lookup can't silently produce origin/
Contributor
Never fall back to HEAD~1 - on a multi-commit branch it scans only the last commit and earlier changes can pass unscanned. Require an explicit base (or the diff-base-free --instruction verification) instead.
Contributor
…gin/HEAD - CI workflow: add explicit step failing the build unless run.json status is 'completed' (budget-truncated runs are 'stopped' yet exit 0) - fix-findings: verify origin/HEAD's target exists before using it as the diff base so a dangling symbolic ref falls through to the fallbacks
Contributor
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
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
2 participants
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.
…ents docs