Menü
Weekly maintenance — reviews dependency PRs and runs any repo-specific weekly tasks defined in running-tend.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Hourly outcome-based analysis of tend's CI behavior — checks whether tend's outputs were accepted or rejected, escalating to session logs only when outcomes look wrong.
Sets up tend — an autonomous junior maintainer for a GitHub repo, powered by Claude or OpenAI Codex — that reviews PRs, triages issues, and fixes CI. Creates config, generates workflows, configures secrets and branch protection via API, creates the bot account, and provisions the harness auth token (Claude OAuth or OpenAI API key). Use when setting up tend on a new repo or when asked to install/configure tend.
Generic CI environment rules for GitHub Actions workflows. Use when operating in CI — covers security, CI monitoring, comment formatting, and investigating session logs from other runs.
Investigates a specific tend GitHub Actions run by downloading its session-log artifacts and parsing the JSONL traces. Surfaces which skill tend loaded, what tools it called with what inputs, files it read or wrote, and where decisions went wrong. Use when asked to "debug a tend run", "investigate a tend run", "why did tend do X", "what did the bot do in CI", "look at the session logs", or to reconstruct tend's behavior step-by-step from a run ID, URL, or PR number.
Debug and fix failing CI on the default branch. Use when CI fails on main.
Reviews a pull request for code quality and correctness. Use when asked to review a PR or when running as an automated PR reviewer.
| name | weekly |
| description | Weekly maintenance — reviews dependency PRs and runs any repo-specific weekly tasks defined in running-tend. |
| metadata | {"internal":true} |
Load /tend-ci-runner:running-in-ci first — it contains CI security rules, review/comment formatting, and polling conventions. This skill posts approvals and comments on PRs, so those rules apply. running-in-ci will also load the repo's running-tend overlay if one exists; keep the loaded content in mind for Step 3.
gh pr list --state open --json number,title,author,labels \
--jq '.[] | select(.author.login == "dependabot[bot]" or .author.login == "renovate[bot]" or (.labels | any(.name == "dependencies")))'
If no dependency PRs are open, note "0 dependency PRs to process" and continue to Step 3 — do not exit; repo-specific weekly tasks may still be due.
gh pr checks <number>tend-review on creation) would otherwise accumulate redundant approvals on the same commit_id:
HEAD_SHA=$(gh pr view <number> --json commits --jq '.commits[-1].oid')
BOT_LOGIN=$(gh api user --jq '.login')
LAST_APPROVAL_SHA=$(gh pr view <number> --json reviews \
--jq "[.reviews[] | select(.author.login == \"$BOT_LOGIN\" and .state == \"APPROVED\")] | last | .commit.oid // empty")
if [ "$LAST_APPROVAL_SHA" = "$HEAD_SHA" ]; then
echo "Already approved on this commit; skipping."
else
# Compose a one-line review body naming the package, bump type, and what you
# checked — e.g. "ruff 0.13 → 0.14 (patch), CI green, no API changes".
gh pr review <number> --approve --body "$REVIEW_BODY"
fi
Perform any weekly maintenance the loaded running-tend overlay defines, following the repo's PR title conventions. If it defines no weekly tasks (or none are due this week), say so in the summary.
Report: dependency PRs processed/approved/skipped (with reasons), and repo-specific weekly tasks completed (or "no repo-specific weekly tasks defined" / "no weekly tasks due").