Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: mcpp-community/mcpp
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: mcpp-community/mcpp
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: docs/style-register
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 22 files changed
  • 1 contributor

Commits on Aug 17, 2026

  1. docs: declarative register throughout, and a checker for the half tha… 

    …t is decidable

The documentation had drifted into a conversational voice: headings phrased as
questions or as asides ("一段话讲完", "打什么由谁决定", "Consuming one", "The
whole idea in one paragraph"), figurative coinages ("姊妹篇", a package's "legs",
sources that "travel"), and the reader addressed as "you"/"你" in reference
material that a person reads to look something up rather than to follow along.

Every heading is now a noun phrase or a declarative statement, and the second
person is gone from the reference documents. Tutorials keep it — 00, 01 and 04
are read while doing, and the list is written down rather than inferred. Quoted
mcpp output keeps its own wording: `did you mean 'x86_64-linux-musl'?` and `your
toolchain : …` are what the program prints, so reproducing them verbatim is a
requirement, not a lapse.

The sweep surfaced four content gaps that no reading would have found:

* docs/zh/05 was missing §2.6, §2.7, §2.7.1, §2.8 and §2.8.3 — five sections of
  a reference manual, including the whole of `[target.*]`;
* docs/zh/05 also had `#### 表形式` filed under the namespace-resolution section
  instead of under `[features]`, which is where its English original sits. Same
  heading COUNT, different structure, which is why the check compares the level
  sequence and not the count;
* docs/zh/10 was missing "manifest keys that need a version floor" and
  docs/zh/README the specifications index;
* docs/12 still said `kind = "shared"` was "Linux/ELF today" in its opening
  example, two days after Mach-O and PE/MinGW landed.

`.agents/skills/mcpp-docs-style` states the rules; `.github/tools/check_docs_style.sh`
enforces the three that are decidable from the text (heading register, second
person, bilingual structure) and runs in ci-linux beside the version-pin check —
same placement, same reason: pure text, no toolchain, and it catches drift that
is invisible to every other job. The skill says plainly which rule the script
cannot check, and it is the most important one: whether a claim's strength
matches its evidence.
    @speak-agent
    speak-agent committed Aug 17, 2026
    Configuration menu
    Copy the full SHA
    3b9539e View commit details
    Browse the repository at this point in the history
Loading