Update Spatie package documentation on spatie.be by re-importing docs for a given repo. Use after merging a PR that touches docs/, or when the user says 'update docs for [package]', 'rebuild docs for [repo]', 'import docs for [repo]', or invokes /update-spatie-docs [repo-name]. Takes a repo name argument (e.g., 'backup', 'laravel-medialibrary', 'laravel-pdf').
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
The spatie.be docs site does not rebuild automatically after a PR merges. To publish doc changes, run the docs:import artisan command against the repo.
Run this twice to be sure (the second run catches any version that lagged on the first pass):
cd /Users/freek/dev/code/spatie.be && ar "docs:import --repo=spatie/{repo_name}"
cd /Users/freek/dev/code/spatie.be && ar "docs:import --repo=spatie/{repo_name}"ar is a shell alias for php artisan remote, so this runs the command against the production spatie.be instance.
If no repo name argument is provided, ask the user for one.
After running, curl a docs URL to confirm the new content is live. The import sometimes returns success before the published pages reflect it, so check a specific page you changed:
curl -sL "https://spatie.be/docs/{repo_name}/v2/some-page-you-changed" | grep -oE '<title>[^<]*</title>'If the title matches the fallback (Introduction page) instead of the page you expected, the cache has not caught up yet. Wait a moment and curl again.
3974caa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.