Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
Lighthouse | Chrome for Developers
Automate web performance audits with Lighthouse
Live code with Tidal Cycles | Tidal Cycles
Live coding environment for making algorithmic patterns
GitHub - jarrodwatts/claude-hud: A Claude Code plugin that shows what's happening - context usage, active tools, running agents, and todo progress
A Claude Code plugin that shows what's happening - context usage, active tools, running agents, and todo progress - jarrodwatts/claude-hud
Announcing Changesets v3 | Changesets
A tool to manage versioning and changelogs with a focus on monorepos
Megaproject Dashboard — Global Infrastructure Tracker
GoogleChromeLabs/wpt-gen
A CLI tool to analyze feature specs and generate the required web platform tests
Managing Changes from Multiple AI Agents
In this video, I walk you through managing changes from multiple AI agents in our to-do app, specifically focusing on the Expert to CSV button. We explore design options using ground agents, where one agent proposes a green design and the other a blue one. After some time, both agents complete their tasks, and their changes are synchronized to GitHub and our local machine. I demonstrate the final designs and decide to ship the green version as the main one. I encourage you to apply this approach in your own projects and consider using rebase in GitHub for similar tasks.
Git AI - Track AI Code all the way to production
Cross-agent observability from prompt to production. Track AI-generated code from Cursor, Claude Code, GitHub Copilot, Gemini, and more through the entire SDLC.
Agent Driven Project Management and Issue Refinement with gh-issue-sync
DiffsHub, from Pierre
View code changes from any public GitHub diff or patch URL with a super-freaking-fast, beautiful, and virtualized interface.
Put State in the Right Place - Delaney Gillilan | SSW 2026
Automated edits - OpenStreetMap Wiki
Automated edits and semi-automated edits (sometimes called mechanical edits) are changes made to OpenStreetMap content with no or very limited human oversight, including those made by bots, algorithmic processes, imports and also major changes made using general-purpose map editing tools such as JOSM. The creation and usage of such tools should conform to the Automated Edits code of conduct and details of edits should be documented on a wiki page in Category:Automated edits log. Undiscussed mechanical edits may be reverted without any discussion, though it may be nice to ask user who made edit before doing that.
Universal Version Control
Building tools to help people explore alternatives, keep track of history, and collaborate better, across all kinds of media.
Code Repository - Git Source Control | Harness
Host Git repositories in Harness, manage pull requests, and connect every commit to secure CI/CD workflows with source-to-deploy traceability.
Graze always works better together! Someone builds a filter once, publishes it, and anyone can drop it into a feed - that's what we call custom nodes. Now, they keep themselves current! Turn on Auto-Update to take every safe release, hold on the ones that need attention, and build with ease!
could hack the overleaf editor/backend with an alternative save function so it saves to PDS instead of github for example or pulls from something like @semble.so or @chive.pub instead of zotero for citations... actually the more I think about this, it actually sounds like a good idea
