一键导入
ops-report
Generate a weekly status summary covering PRs opened/merged/closed by Albert, issues triaged, spec alignment progress, and blockers awaiting human input.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate a weekly status summary covering PRs opened/merged/closed by Albert, issues triaged, spec alignment progress, and blockers awaiting human input.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Triage incoming GitHub issues across supervised Altertable repositories. Use when processing new issues, labeling bugs and feature requests, detecting duplicates, requesting minimal reproductions, or marking stale issues.
Notification-driven maintainer routine to identify actionable work across supervised Altertable repositories. Relies on GitHub notifications and API to monitor activity and respond to issues and PRs requiring attention. Use when starting a maintenance session to process notifications and prioritize work.
Bootstrap or update an Altertable SDK repository from a versioned API spec. Use when given a target GitHub repository (e.g. altertable-ai/altertable-lakehouse-ruby) and a spec version tag (e.g. v0.1.0) to set up a git submodule, implement missing functionality, and submit a PR. Also use when a new spec version is released and the SDK needs to be updated to match.
Defines conventions for releasing open-source SDKs and libraries. Use when releasing a new version of an SDK, writing changelogs, or publishing to a language registry (npm, PyPI, Maven, etc.).
Keep shared configuration, community files, and CI templates consistent across all SDK repositories. Use when auditing cross-repo consistency or propagating a change (license, contributing guidelines, CI updates, bot config) to multiple SDK repos.
Review community pull requests against Altertable SDK standards. Use when reviewing contributor PRs, checking naming conventions, test coverage, changelog entries, and deciding whether to approve, request changes, or close.
基于 SOC 职业分类
| name | ops-report |
| description | Generate a weekly status summary covering PRs opened/merged/closed by Albert, issues triaged, spec alignment progress, and blockers awaiting human input. |
Weekly status report. Run on Friday full heartbeat or on demand.
Rules: safety · communication · memory
spec-status.sh --markdown# PRs authored by Albert in the last 7 days across all supervised repos
gh search prs \
--author albert20260301 \
--updated ">=$(date -u -d '7 days ago' +%Y-%m-%d 2>/dev/null || date -u -v-7d +%Y-%m-%d)" \
--json title,url,state,repository,createdAt,mergedAt \
--limit 100
# Issues commented or labeled by Albert
gh search issues \
--involves albert20260301 \
--updated ">=$(date -u -d '7 days ago' +%Y-%m-%d 2>/dev/null || date -u -v-7d +%Y-%m-%d)" \
--json title,url,state,repository,labels \
--limit 100
# Spec alignment
bash scripts/spec-status.sh --markdown
# Full ecosystem health (supplementary to spec-status.sh)
# Reports: spec alignment, open PR count, open issue count, CI status per repo
bash scripts/ecosystem-status.sh --markdown
Produce a markdown document using this template:
# Albert — Weekly Report (YYYY-MM-DD)
## PRs This Week
### Opened
| Repo | PR | State |
|------|----|-------|
| ... | [#N title](url) | open / merged / closed |
### Merged
- ...
### Closed Without Merge
- ...
## Issues Triaged
| Repo | Issue | Action |
|------|-------|--------|
| ... | [#N title](url) | Labeled `bug`, commented, closed (duplicate of #M) |
## Spec Alignment
<output of spec-status.sh --markdown>
## Blockers Awaiting Human Input
- [ ] PR [#N](url) in `altertable-ruby` — needs François to approve before merge.
- [ ] Issue [#M](url) — unclear requirements; tagged `needs-clarification`.
## Planned Next Actions
- Run `sdk-sync` for repos still missing `SECURITY.md`.
- Open submodule bump PRs for outdated SDKs once spec v0.X.Y is tagged.
spec-status.sh --markdown output