Skylos Cloud · Chapter 13: Setting team policy Decide once what fails a pull request. Every repository, every laptop and every pull request then gets the same answer.
Step 1: Open Policy Policy lives under Governance in the sidebar. Admins and owners can change it; everyone else can read it.
Step 2: One page, five parts Quality gate, Coding agents, Supply chain, Custom rules and History. One Save covers them all.
Step 3: Start from the default A new workspace blocks any new issue. Critical security issues always count, and exposed secrets are caught by that same rule.
Step 4: Edit the conditions Start from a preset (Recommended, Stricter on AI code or Strict) or set the rules yourself. Nothing is saved until you press Save.
Step 5: Allow a few, block what matters For older repositories: allow a handful of new medium and low issues, and keep critical and high at zero.
Step 6: Always block exposed secrets Tick this so secrets stay blocked even if someone loosens the limits later.
Step 7: Say why Skylos lists every change before you save. The reason is kept with this version in Policy history.
Step 8: Preview before you save Preview re-checks the latest scan of every repository against the new rules. Nothing is saved yet.
Step 9: Save it Each save becomes a new version. Repositories that inherit the policy use it on their next upload.
Step 10: Stop repositories loosening it Turn this on and a repository can make its own policy stricter, never looser.
Step 11: Rules for code an AI agent wrote Turn on agent rules, then choose Block, Warn or Off for each signal, such as weakened tests or a made-up package.
Step 12: Supply chain Block malware, hold brand-new package releases, and name your internal packages so look-alikes on public registries are blocked.
Step 13: Your own rules Custom rules add checks for patterns the built-in rules miss. They run in the CLI and on every pull request.
Step 14: Every change is a version Policy history shows who saved each version, when and why. Restoring an old one saves it again as a new version.
Step 15: Check a branch from your laptop skylos cloud --gate scans, uploads the findings and exits 1 when the team policy fails the branch.
Step 16: See why in Skylos Cloud The link opens the branch: the condition that failed, its limit and the count in this scan. A lead can still choose Merge anyway, with a recorded reason.
Recap Policy → Edit conditions · Reason for change, then Preview impact · Apply to every repository (stricter only) · Coding agents, Supply chain, Custom rules · History → Restore this version · skylos cloud --gate