// Detect user-facing features in recently merged PRs and open a PR in the docs repo adding the missing documentation.
Generate a customer-specific enterprise service agreement by filling in the standard template with deal details.
Head of Data agent - creates reportings and ad-hoc analytics using nao MCP tools. Always use ask_nao to create conversations that persist in nao.
Review a contract against standard negotiation positions - flag deviations, generate redlines, provide business impact analysis. Use when reviewing vendor or customer agreements, when you need clause-by-clause analysis, or when preparing a negotiation strategy.
Create a new skill from scratch. Generates the SKILL.md, registers it in AGENTS.md, and sets up the content folder structure.
Set up an AI agent by validating her scope, schedule, and delivery channel. Run as `/sylph-setup-agent <agent-name>` or `/sylph-setup-agent all`.
Personalize Sylph to your company. Ask the company name, then derive everything from the web - CONTEXT.md, brand voice, team, ICP, and standing instructions.
| name | update-docs |
| description | Detect user-facing features in recently merged PRs and open a PR in the docs repo adding the missing documentation. |
When the user runs /update-docs, scan recently merged PRs for user-facing
changes and open a documentation PR.
| Connector | Purpose |
|---|---|
| GitHub | Read merged PRs, create docs PRs |
Both repos must be cloned locally:
State file: agents/cmo/_state/docs_last_refresh.txt (plain text, single ISO date).
agents/cmo/_state/docs_last_refresh.txt if it existsSINCEtoday - 15 days as SINCETODAY as the date to write back at the endgh pr list -R <product-repo> \
--state merged \
--search "merged:>=<SINCE>" \
--limit 100 \
--json number,title,url,mergedAt,body,author,files
Keep the full list - every PR appears in the final summary, even those that don't need docs.
For each PR, decide: user-facing or not?
User-facing (needs docs):
NOT user-facing (skip):
When unsure, read the PR body and changed files. If still ambiguous, err on no docs and note it in the summary.
Pull latest from the docs repo:
cd <docs-repo> && git checkout main && git pull
Before writing any new doc, search the repo for existing coverage (grep on keywords from the PR title/body). If a relevant page exists, update it instead of creating a new one.
For each user-facing PR that needs docs:
cd <docs-repo>
git checkout -b docs/refresh-<TODAY>
git add <changed files>
git commit -m "docs: refresh for PRs merged since <SINCE>"
git push -u origin docs/refresh-<TODAY>
gh pr create -R <docs-repo> \
--title "docs: refresh for PRs merged since <SINCE>" \
--body "<PR summary - see template below>"
Every PR from Step 2 must appear in the list, in merge order. Use these exact shapes:
- PR merged #123 <PR title> - no docs added
- PR merged #124 <PR title> - added docs - <one-line description of what was documented and where>
No other bullet shapes. No section grouping. Keep it a flat list.
If zero PRs were user-facing, skip PR creation and just update the state file.
Write TODAY (ISO date) to agents/cmo/_state/docs_last_refresh.txt:
echo "<TODAY>" > agents/cmo/_state/docs_last_refresh.txt
git add agents/cmo/_state/docs_last_refresh.txt
git commit -m "chore(cmo): log docs refresh <TODAY>"
git push
The next run picks up from this date.
Return to the user:
After the docs PR is reviewed and merged:
_insights.md with patterns: which PRs consistently need docs, which doc styles get approved without changes