Skip to content

pentest skill cloud cli - #1220

Merged
bearsyankees merged 3 commits into
mainfrom
devin/1788288371-pentest-skill-cloud-cli
Sep 1, 2026
Merged

pentest skill cloud cli#1220
bearsyankees merged 3 commits into
mainfrom
devin/1788288371-pentest-skill-cloud-cli

Conversation

@bearsyankees

Copy link
Copy Markdown
Collaborator

No description provided.

@bearsyankees
bearsyankees merged commit d26b1ab into main Sep 1, 2026
2 checks passed
@greptile-apps

greptile-apps Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR updates the penetration-testing workflow to present the managed platform through the new strix cloud CLI rather than a REST-only example.

  • Adds device-flow login and optional scope guidance.
  • Documents domain registration, verification, scan execution, and vulnerability listing.
  • Adds local-source upload, billing top-up, and non-TTY JSON-output guidance.

Confidence Score: 3/5

The PR should not merge until the local-source and billing examples are made executable in the documented agent workflows.

The source-upload example fails in non-interactive environments without explicit approval, while the billing top-up example omits the CLI's required credit amount.

Files Needing Attention: skills/penetration-testing-with-strix/SKILL.md

Important Files Changed

Filename Overview
skills/penetration-testing-with-strix/SKILL.md Replaces the managed REST example with cloud CLI commands, but the source-upload and billing examples omit arguments required for their documented execution paths.
Prompt To Fix All With AI
### Issue 1
skills/penetration-testing-with-strix/SKILL.md:149
**Source Upload Lacks Approval**

When an agent or CI process runs `strix cloud scans start --source .` non-interactively, the CLI rejects the upload because neither `--yes` nor `--approve-sha256` is supplied, so the documented code-review scan never launches.

```suggestion
For a local repository, `strix cloud scans start --source . --yes` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts.
```

### Issue 2
skills/penetration-testing-with-strix/SKILL.md:149
**Topup Omits Required Credits**

When credits run out and the documented `strix cloud billing topup` command is used, argument parsing fails because the required `--credits` integer is absent, so the Stripe challenge does not start.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "Shorten the scopes note in the cloud log..." | Re-trigger Greptile

```

Ask the user to create the token (and register the target as a domain/repository asset) if they have not. If Docker/local prerequisites are not already satisfied, use this path instead of trying to install infra.
For a local repository, `strix cloud scans start --source .` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Source Upload Lacks Approval

When an agent or CI process runs strix cloud scans start --source . non-interactively, the CLI rejects the upload because neither --yes nor --approve-sha256 is supplied, so the documented code-review scan never launches.

Suggested change
For a local repository, `strix cloud scans start --source .` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts.
For a local repository, `strix cloud scans start --source . --yes` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts.
Prompt To Fix With AI
This is a comment left during a code review.
Path: skills/penetration-testing-with-strix/SKILL.md
Line: 149

Comment:
**Source Upload Lacks Approval**

When an agent or CI process runs `strix cloud scans start --source .` non-interactively, the CLI rejects the upload because neither `--yes` nor `--approve-sha256` is supplied, so the documented code-review scan never launches.

```suggestion
For a local repository, `strix cloud scans start --source . --yes` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts.
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

```

Ask the user to create the token (and register the target as a domain/repository asset) if they have not. If Docker/local prerequisites are not already satisfied, use this path instead of trying to install infra.
For a local repository, `strix cloud scans start --source .` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Topup Omits Required Credits

When credits run out and the documented strix cloud billing topup command is used, argument parsing fails because the required --credits integer is absent, so the Stripe challenge does not start.

Prompt To Fix With AI
This is a comment left during a code review.
Path: skills/penetration-testing-with-strix/SKILL.md
Line: 149

Comment:
**Topup Omits Required Credits**

When credits run out and the documented `strix cloud billing topup` command is used, argument parsing fails because the required `--credits` integer is absent, so the Stripe challenge does not start.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant