Add a short maintainer guide for merge:batch and link it from the
existing merge policy docs.
Lock in the source-validation CI fixes discovered during the
merge-batch end-to-end exercise so shallow checkout and missing
base-branch fetch regressions fail the workflow contract test.
Add maintainer guidance for npm installer packaging so future
release work treats missing runtime dependencies as a release
blocker and covers the path with runtime-aware tests.
Refs #445
Make post-merge credits maintenance mandatory on every PR merge. Require maintainers to sync Repo Contributors, audit Official Sources and Community Contributors, and push any README credit updates immediately instead of deferring them to release prep.
Document the current static web-app behavior, local-only save flow, shallow installer path, and maintainer-only sync controls.\n\nAlign maintainer guides with the active audit-to-risk-sync workflow, canonical artifact bot contract, release/coverage requirements, and updated security triage context so the docs match the repository's real operating model.
Freeze the accepted validation warning count at 135 so repo-state and release-state checks fail if the warning baseline grows silently while legacy warnings remain intentionally preserved.
Add a read-only maintainer audit command plus regression tests so maintainers can inspect repo health quickly without mutating files.
Unify main-branch maintenance around repo-state and release-state commands so generated docs, contributor acknowledgements, tracked web assets, and canonical artifacts stay aligned across CI and scheduled hygiene runs.
Harden release publication by reusing deterministic sync commands, adding package dry-run verification, and covering the new workflow contract with regression tests.
Add maintainer automation for repo-state hygiene so contributor acknowledgements, count-sensitive docs, and GitHub About metadata stay aligned from the same workflow.
Cover the new scripts with regression tests and wire them into the local test suite to keep future maintenance changes from drifting silently.
Update the Claude marketplace entry to use a schema-valid relative source path and add a regression test so invalid marketplace sources fail in the local suite. Also document the maintainer workflow used for stale PR metadata and fork-gated Actions runs.
Fixes#344
- Document step-by-step flow to reopen closed PRs and merge via GitHub
- Add agent instruction block: always merge via GitHub, never close after
local integration; if closed, reopen and merge for contributor credit
- Add shortcut link for Reopen & merge a closed PR
- Add docs/maintainers/merging-prs.md: policy to always use Squash and merge,
resolve conflicts on PR branch so PR shows Merged; Co-authored-by for rare
local integration
- Update .github/MAINTENANCE.md: merge via GitHub only, never close after
local integration; conflict resolution on branch then merge
- Update CONTRIBUTING.md Recognition: we always merge accepted PRs on GitHub,
never close after integrating locally
Addresses feedback from @sraphaz on #225 (attribution when PRs are integrated
locally). Going forward PRs will show as Merged so contributors get full credit.
Consolidate the repository into clearer apps, tools, and layered docs areas so contributors can navigate and maintain it more reliably. Align validation, metadata sync, and CI around the same canonical workflow to reduce drift across local checks and GitHub Actions.
- Add maintainer shortcuts and step-by-step 'When you merge a PR'
- Add post-merge routine and when to close issues (Closes #N, manual)
- Add release checklist, tag/package.json note, release_notes guidance
Co-authored-by: Cursor <cursoragent@cursor.com>
- Align package.json description to 883+ skills
- Allow risk:unknown in validate_skills.py for legacy skills
- Add When to Use section to 6 skills; fix frontmatter in brainstorming, agents-v2-py, hosted-agents-v2-py
- Add scripts/validate_references.py for workflows, bundles, BUNDLES.md links
- Update QUALITY_BAR and SKILL_ANATOMY; add docs/AUDIT.md and MAINTENANCE note for data/
- Make YAML frontmatter test warn instead of fail; regenerate catalog and index
Co-authored-by: Cursor <cursoragent@cursor.com>
Prepare release 5.0.0 by documenting the new Workflows foundation, bumping package metadata, refreshing release notes, and extending MAINTENANCE guidance for workflows consistency and issue-closing protocol.
Co-authored-by: Cursor <cursoragent@cursor.com>
- Add npm scripts: validate, validate:strict, index, readme, chain, catalog, build
- Align docs to V4 and 560 skills (GETTING_STARTED, FAQ, BUNDLES, MAINTENANCE, vietnamese)
- build-catalog: output to data/ for catalog, bundles, aliases; add to CI and drift check
- Add yaml dep, Node setup and catalog step in CI; extend auto-commit and drift msg
- Translate CI and MAINTENANCE to English; update CI_DRIFT_FIX and maintenance routine
- QUALITY_BAR/CONTRIBUTING: canonical validator npm run validate; legacy note in validate-skills.js
- allinea conteggi skill a 256 in README/GETTING_STARTED
- corregge anchor e TOC per Full Skill Registry
- rimuove emoji dagli H2 e unifica Repo Contributors
- sistema il blocco Regenerate Index in MAINTENANCE
