docs: add run logging and Slack notifications to aeo_crosslink_audit skill#234
Open
rachaelrenk wants to merge 6 commits into
Open
docs: add run logging and Slack notifications to aeo_crosslink_audit skill#234rachaelrenk wants to merge 6 commits into
rachaelrenk wants to merge 6 commits into
Conversation
Add high-confidence internal cross-links for the agents, cloud agents, and orchestration topic area, grounded in Peec AEO signals (scheduling, managing and observing multiple agents) and existing docs: - Scheduled Agents reference now links to the Scheduled Agents quickstart for a guided, no-CLI setup path. - Run multiple agents at once guide now links to Agent notifications and the Agent Management Panel for notification setup and run observability. Co-Authored-By: Oz <oz-agent@warp.dev>
Transfer changes from PR #232 (docs/aeo-crosslinks-agents-orchestration-20260616): - integrations/index.mdx: add managing-cloud-agents cross-link - triggers/index.mdx: add managing-cloud-agents cross-link after trigger types Co-Authored-By: Oz <oz-agent@warp.dev>
…skill - Add .agents/logs/aeo_crosslink_audit_runs.md as a durable run log committed to main after every scheduled run (PR or no-change) - Add Environment requirements section documenting SLACK_BOT_TOKEN and SLACK_CHANNEL_ID (same secrets already used by weekly-404-monitor) - Add workflow steps 7 and 8: write run log entry, then post simple text notification to #growth-docs; both fall back to run output gracefully - Add Run log format and Slack notification format reference sections - Update stale manual-sharing note in no-change report section Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
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 |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR adds observability instructions for the aeo_crosslink_audit skill, including a run log and Slack notifications, plus several docs cross-link edits.
Concerns
- The new run-log step tells future agents to commit directly to
mainafter opening a PR, but it does not require a cleanmaincheckout/worktree or staging only the log file. That can accidentally push the PR's unreviewed docs edits tomain; see inline comment. - The new log file header says entries are appended, while the skill requires prepending new entries below the separator; see inline suggestion.
Verdict
Found: 0 critical, 1 important, 1 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
- Step 7: specify clean main checkout/worktree and path-limited staging to prevent accidentally pushing PR branch edits to main alongside log - Log file header: 'Appended' -> 'New entries are prepended' to match the skill's actual prepend instruction Co-Authored-By: Oz <oz-agent@warp.dev>
rachaelrenk
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
aeo_crosslink_auditskill now runs on a schedule, but has no self-reporting: it's impossible to answer whether the automation is producing durable value over time without replaying individual Oz runs. Team members also have to manually paste Oz run links into#growth-docsto loop in reviewers — whether a PR was opened or not.What this PR does
Adds two observability improvements (parts A and B of the AEO automation: run observability and team notifications tracking item):
A: Run log (
.agents/logs/aeo_crosslink_audit_runs.md)After every run — whether a PR is opened or a no-change report is written — the agent prepends a structured 7-field entry to this new log file and commits it directly to
mainfrom a clean worktree (staging only the log file, so no unreviewed PR edits can leak). Fields: date, run ID, source signals, PR link, links proposed/added, pages touched, themes, and no-change reason.B: Slack notification (step 8 in
aeo_crosslink_auditworkflow)After writing the log entry, the agent posts a short plain-text message to
#growth-docsusingSLACK_BOT_TOKENandSLACK_CHANNEL_ID(the same secrets already in thebuzzOz environment fromweekly-404-monitor). Fires on every run — PR-opened and no-change alike. Both the log write and Slack post fall back gracefully to run output if secrets or git push are unavailable.Files changed
.agents/skills/aeo_crosslink_audit/SKILL.md— added Environment requirements section, workflow steps 7–8, Run log format and Slack notification format reference sections.agents/logs/aeo_crosslink_audit_runs.md— new log file (empty, ready for first entry)Before merging
Confirm
SLACK_BOT_TOKENandSLACK_CHANNEL_IDare set in thebuzzOz environment (almost certainly already there fromweekly-404-monitor).Success criteria
After merging, the team can assess whether observability by assessing the following:
Generated with Oz
Co-Authored-By: Oz oz-agent@warp.dev