Repository navigation
Add a weekly, measured upstream sync - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds
/upstream-sync, a weekly routine for taking ideas from eight similar projects without lowering the bar for what ships. It is a project skill under.claude/skills/upstream-sync/and is not part of the published skill.The eight repos are slop-score, antislop-sampler, unslop and humanize, which publish measurements, and humanizer, stop-slop, no-ai-slop and avoid-ai-writing, which mostly contribute pattern lists.
sync.pykeeps a shallow clone of each one in.upstream/, which git ignores. It follows the default branch of each repo, even when the owner renames it. It records the last commit read inupstream.json, so next week's session only reads what changed after it.A session goes like this. First, the agent reads the diffs and proposes candidates, and each one says how it will be measured. I choose which ones to try. Each one I pick gets ported to our Python and measured on its own, before the change and after it. A candidate ships only if it clears the bar written in the skill: for detection, AUC rises and human texts are not flagged more often; for rewrite rules, it wins on
devwith p < 0.10 and does not get worse ontest. Word lists are scored entry by entry. When nothing ships, the PR carries onlyupstream.json.AGENTS.mdused to be a git symlink and is now a real copy ofCLAUDE.md. Windows clones checked the symlink out as a nine-byte text file.CLAUDE.mdgains one line pointing to the new skill.Tests:
python3 -I .claude/skills/upstream-sync/test_sync.pypasses all 11, which use local git repos as upstreams. A realupdatecloned all eight repos.Design and plan are in
.claude/specs/.