Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
It's good to see a style guide that covers not just coding but also logical structures. Someone also made an agent skill out of this guide (0xMassi/google-rust-style-skill) #rustlang #opus #codex google.github.io
@zachlloydtweets same split worked for my rust style skill. 21 of the google rules went straight into rustfmt and clippy config, versioned and enforced. the other 40 are judgment calls the agent reads as text, and those are the ones that drift between runs 0xMassi/google-rust-style-skill
@Debt__free__ @ManishEarth made one: npx skills add 0xMassi/google-rust-style-skill then ask your agent to review the crate against google rust style. 0xMassi/google-rust-style-skill
@ManishEarth @illulachy_ i mapped this while building the skill: 21 rustfmt/clippy settings cover the checkable parts, each tied to its guide section, the rest stays prose. could be a starting list for the upstreaming: 0xMassi/google-rust-style-skill
@marckohlbrugge "idiomatic rust" is the vague part of that prompt. google just open sourced the style guide they use, so i turned it into a skill: the agent gets a concrete target plus clippy config to check itself against. 0xMassi/google-rust-style-skill