chore: align weekly-404-monitor skill with Docs Agent environment - #394
chore: align weekly-404-monitor skill with Docs Agent environment#394rachaelrenk wants to merge 2 commits into
Conversation
- Use BUZZ_SLACK_TOKEN (matches existing secret in K5KStCm5aYvhfBJb8cHol6) - Hardcode #growth-docs channel ID (C09BVK0PL3Y) instead of env var - Update environment reference from 'buzz' to 'Docs Agent' - Require --draft flag on gh pr create - Add oz-dev schedule create command to Scheduling section Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR updates the weekly-404-monitor skill to match the Docs Agent environment: it switches the Slack token reference to BUZZ_SLACK_TOKEN, documents the hardcoded #growth-docs channel ID, requires draft PRs for redirect automation, and adds the one-time schedule creation command.
Concerns
- No blocking concerns found in the annotated diff.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Summary
Aligns the
weekly-404-monitorskill config with how the other scheduled doc agents run, so the next scheduled run opens PRs under @oz-by-warp and is visible in oz.warp.dev.Changes
SLACK_BOT_TOKEN→BUZZ_SLACK_TOKEN(matches the secret already provisioned in the Docs Agent environmentK5KStCm5aYvhfBJb8cHol6)GROWTH_DOCS_SLACK_CHANNEL_IDenv var requirement; hardcodedC09BVK0PL3Y(#growth-docs) directly, matching thevalidate_ui_refsskill patternbuzztoDocs Agent(K5KStCm5aYvhfBJb8cHol6)--draftrequirement togh pr createso agent-generated redirect PRs always need human review before mergingoz-dev schedule createcommand as the canonical one-time setup stepNext step after merging
Once this lands on
main, register the schedule (once) from the Docs Agent environment:Co-Authored-By: Oz oz-agent@warp.dev