Skip to content

merge queue: checking main (91cd681), #12001 and #11975 together#12003

Draft
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/6cf2909627
Draft

merge queue: checking main (91cd681), #12001 and #11975 together#12003
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/6cf2909627

Conversation

@mergify

@mergify mergify Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged when the schedule will match. 🎉

Branch main (91cd681), #12001 and #11975 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11975.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 624772f231f0fc69c3086e0ba625f916e04f53d3
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 11975
    scopes: []
scopes: []
...

jd and others added 4 commits June 30, 2026 17:44
Add four project skills that compose into one docs workflow:

- document-a-feature: end-to-end orchestrator (placement, component
  selection, writing, navItems/_redirects/SEO plumbing, proofread +
  config validation + build check)
- capture-screenshots: Chrome MCP dashboard screenshots with consistent
  viewport, correct images/ path, and ready-to-paste astro:assets snippet
- validate-config-examples: extract and classify YAML fences, validate
  real Mergify configs via `mergify config validate`
- docs-gap-analysis: diff shipped product (PRs/Linear/changelog) against
  docs to surface undocumented/partial/stale features

docs-gap-analysis finds the work, document-a-feature does it and calls the
other two as tools; all reuse the existing mdx-documentation and proofread-*
skills rather than duplicating them. No changelog skill by design (changelog
entries are autogenerated and must not be touched).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: Ie17e7c5434df6122f99d1904ae9eeaf6e71f2211
The Mergify plugin is now published as a single unified `mergify` plugin on
the built-in `claude-plugins-official` marketplace. Replace the three-command
install (add the `Mergifyio/mergify-cli` marketplace, install
`mergify-stack@mergify`, reload) with a single:

    /plugin install mergify@claude-plugins-official

Since the official marketplace ships with Claude Code, there's nothing to add
first. The unified plugin bundles every Mergify skill (Merge Queue, CI
Insights, config validation, scheduled freezes), so the tips are updated
accordingly and the obsolete third-party auto-update tip is dropped.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I91db52200925f4707f5226dc795a047d9678dcaf
@mergify mergify Bot deployed to Mergify Merge Protections July 1, 2026 19:43 Active
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant