Repository navigation
ProSEO 1.0.1
Maintenance release: contributor setup, a leak guard that no longer names what it protects, and documentation fixes. No skill behaviour changes, and existing runtimes stay valid — no need to re-run /pro-seo setup.
Added
- CONTRIBUTING.md, issue forms for bugs, feature requests and licensing questions, and a pull request template
- Private vulnerability reporting is enabled, as SECURITY.md describes
plugin.jsonnames the repository; its homepage is the documentation site, https://pro-seo.info
Changed
- The CI leak guard reads its private patterns from a repository secret and reports matches by location only
- CI uses
actions/checkout@v5andactions/setup-python@v6
Fixed
CLAUDE.mdandAGENTS.md: orchestrator path (skills/pro-seo/), and the lifecycle, keywords, internal-links, refresh, migration and report skills plussetupanddoctorwere missingCLAUDE.mdlisted a script that does not ship instead ofruntime.py- The orchestrator's sub-skill breakdown
- Version labels and
.gitignoreentries inherited from the upstream project
Update
/plugin marketplace update pro-seo
New install:
/plugin marketplace add theahmadraza/ProSEO
/plugin install pro-seo@pro-seo
/pro-seo setup
Verifying this release
release-manifest-v1.0.1.json lists a SHA-256 for every tracked file. Check a checkout against it with python scripts/release_sign.py --compare release-manifest-v1.0.1.json <(python scripts/release_sign.py).
Full changes in CHANGELOG.md.