Skip to content
PETROVA

Refusal conditions

Refusal conditions (both skills)

Section titled “Refusal conditions (both skills)”

These conditions cause petrova-act and petrova-status to refuse the action and surface the reason to the user. They are deliberate — refusal is correct behaviour, not a failure.

  • Target repo’s slug not present in registry.yaml → refuse, list known slugs, suggest opening an onboarding PR.
  • Write verb invoked with --apply and auth env vars unset → refuse, instruct to set credentials.
  • Privileged paths (.github/workflows/, *.env, secrets/, deploy/credentials/) appearing in any write verb’s files → refuse unconditionally; humans edit those.
  • Skill cannot determine the current repo’s slug from git remote get-url → refuse and ask for explicit --repo <slug> from the human.

Source: skills/README.md § “Refusal conditions”.