SECOPS
Pull Request Secret Gate that Blocks Merge Until Cleared
On every pull request, scans the changed files for secrets and posts a blocking status check; if a secret is detected it fails the check, comments the exact location.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updatedGitHub
- LogicScan PR diff for committed secrets
- ActionSet passing or failing commit status checkGitHub
- ActionPost review comment with masked match locationGitHub
- OutputAssign remediation ticket to PR author in LinearLinear
What it does
This workflow acts as a required status check on pull requests. It scans the PR diff for embedded credentials and sets the commit status to failure when one is present, preventing merge until the developer removes the secret and re-pushes.
When to use it
Use it when you want to stop secrets before they ever land on the default branch. Unlike the push scanner, this is a pre-merge gate, so the bad code never enters the protected history in the first place.
How it works
- 1A GitHub pull_request event (opened or synchronize) triggers the run.
- 2A logic step diffs the PR and tests each added line against secret detectors.
- 3If no secret is found, an action sets the commit status to success so merge is allowed.
- 4If a secret is found, an action posts a failing commit status plus a review comment pinpointing the file and line with the value masked.
- 5A Linear ticket is created and assigned to the PR author with a remediation checklist as the final output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.