Skip to content

docs: streamline maintainer and contributor guides - #94

Merged
WilliamBergamin merged 4 commits into
mainfrom
imporve-maintainers-guide
Jul 16, 2026
Merged

docs: streamline maintainer and contributor guides#94
WilliamBergamin merged 4 commits into
mainfrom
imporve-maintainers-guide

Conversation

@WilliamBergamin

@WilliamBergamin WilliamBergamin commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

This pull request tidies up the repo's contributor- and maintainer-facing docs and brings them under markdown linting.

Preview

Testing

  • make lint passes (now covering the three newly-included .github/*.md files).
  • make test-unit passes.
  • Skim the rendered .github/maintainers_guide.md and .github/contributing.md on the branch and confirm the intra-doc anchor links (e.g. "Updating Changesets", "Local Development & Testing") resolve.

Notes

  • Docs / repo-meta only, so no changeset is included (per the maintainers guide, documentation updates don't require one).

Requirements

Replace the duplicated make-target listings in the maintainers guide and
AGENTS.md with a pointer to `make help`, so the docs can't drift from the
Makefile. Drop decorative emoji from section headings (which also repairs
the broken `#-updating-changesets` style anchors), fix the CODEOWNERS
description, and normalize em-dash asides to colons.

Bring `.github/maintainers_guide.md`, `.github/contributing.md`, and
`.github/CODE_OF_CONDUCT.md` under rumdl linting via the `[tool.rumdl]`
include list, and fix the heading levels, list formatting, and anchor
links they surfaced.

Convert the PR template's placeholder prompts from parentheses to HTML
comments so they don't leak into submitted PR bodies.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@changeset-bot

changeset-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0f390c0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@WilliamBergamin WilliamBergamin self-assigned this Jul 14, 2026
@WilliamBergamin WilliamBergamin added docs Improvements or additions to documentation chore Maintainer work: repo files, release scaffolding, general maintenance build Changes to compilation and CI processes labels Jul 15, 2026
@WilliamBergamin
WilliamBergamin marked this pull request as ready for review July 15, 2026 13:52
@WilliamBergamin
WilliamBergamin requested a review from a team as a code owner July 15, 2026 13:52

@mwbrooks mwbrooks left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Thanks for adding markdown linting. This is very nice! 🙇🏻

✏️ I left a comment that's non-blocking around keeping our document make commands to make it easier for humans and agents to find common commands with less effort (mental or token usage). While documenting the help command to capture new, undocumented commands.

### Summary

(Please describe the goal of this pull request and mention any related issue numbers)
<!-- Please describe the goal of this pull request and mention any related issue numbers -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

comment: If we use HTML comments, I don't think they'll appear to the developer when the person is writing the pull request on GitHub. I don't think this is a big deal - but we need to leave these hints for the issue templates.

Comment thread AGENTS.md Outdated
| `make clean` | Remove .venv |
| `make cursor-install` | Install this plugin into a local Cursor for development |
| `make cursor-uninstall` | Uninstall this plugin from the local Cursor install |
Run `make help` for the full list of targets and what each does. See the [maintainers guide](.github/maintainers_guide.md#local-development--testing) for local development and testing setup.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought: This is fine, but I had to admit that I prefer both informing the agent to run help but also giving the explicit commands. It reduces the loops & tokens (seeing the commands immediately) and still gives flexibility for undocumented command (running help).

Comment thread .github/maintainers_guide.md Outdated
make format # Auto-format: Ruff for Python, rumdl --fix for Markdown
make typecheck # Mypy static type checks
```
Run `make help` to see the available targets and what each one does. It reads the

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought: Personally, I'd rather have these explicit commands. As a maintainer, I'm often searching for something specific like "test" because I'm looking for the documented command. By just documenting help, it makes it harder for me to find what I'm looking for.

My suggestion would be to add help to the list of documented commands - in case there are undocumented commands.

Comment thread pyproject.toml
Comment on lines +57 to +59
".github/maintainers_guide.md",
".github/contributing.md",
".github/CODE_OF_CONDUCT.md",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: Is there value is using a wildcard here instead?

Suggested change
".github/maintainers_guide.md",
".github/contributing.md",
".github/CODE_OF_CONDUCT.md",
".github/**/*.md",

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think using a wildcard here might mess up some of our templates 🤔

WilliamBergamin and others added 2 commits July 16, 2026 11:26
Address PR review: keep the documented make commands explicit so humans
and agents find common commands without running help, while retaining the
`make help` pointer for undocumented targets. Descriptions are aligned to
the Makefile's own help text (e.g. `make clean` also removes the Cursor
install). Also refresh the now-stale rumdl scope sentence to mention the
.github/ docs added to the include list in this PR.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@WilliamBergamin
WilliamBergamin enabled auto-merge (squash) July 16, 2026 16:35
@WilliamBergamin
WilliamBergamin merged commit e75b0cf into main Jul 16, 2026
7 checks passed
@WilliamBergamin
WilliamBergamin deleted the imporve-maintainers-guide branch July 16, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Changes to compilation and CI processes chore Maintainer work: repo files, release scaffolding, general maintenance docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants