Activity
Stars and mentions · Last 30 days, Oct 13 – Nov 11
Top repositories
quality-sh’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside quality-sh’s account where quality-sh opened or reviewed pull requests in the past 365 days.
Who noticed quality-sh
Everyone who starred or forked quality-sh’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories quality-sh owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Show HN: Provenance – A Spec That Evolves with Your Code Hi all, I've been building Provenance, a tool for growing your specification of your code as your understanding of it becomes clearer. Currently I feel that the lifecycle around software improving feels too detached. We talk to our teams, spec things out with our agents, track work in tickets, but there's nothing really to connect it all together and there's no neat way to keep it all updated. Provenance is my attempt to solve that problem by building direct links between planning, requirements, implementation, and verification. I've purposely tried to keep the concepts as agnostic to everyone's own workflows as possible. I'll go over some of them here: Sources: a source is anything you can link to that might be of value to understanding your software. I.e. a diagram, meeting notes, legislation, a video even. Requirement: a requirement is a high level description of some need of your system. Resolution: A resolution is a decison made about some property of your system you believe needs to be documented. Generally resolutions are the child of one or more requirements and the parent many requirements. Rule: A rule is the child of a requirement used to describe some single property of a requirement. Rules are linkable directly to functions that implement them and tests that verify them. We're still in the early stages, but I'd be interested to see what you all think.