Repository navigation
docs(skills): count the one-per-curator day in the owner's timezone and write down the lint checks that cannot go red - #22
Merged
Conversation
…nd write down the lint checks that cannot go red
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 4
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
The one-submission-per-curator-per-day rule never said what a day was. Last night a drain opened PRs just after local midnight that were still the previous UTC day, and under a UTC reading they broke the rule while the maintainers saw two PRs a day apart. Both skills now say the day is a calendar day in the one timezone the owner names at the top of the ledger.
The same drain found checks that pass without proving anything: a catalogue builder that exits 0 and writes its errors to a file, a loader that warns and skips a malformed entry, a hardened python -I that fails on an import CI never trips over, and a spell check that lets a near-miss typo through. submit-awesome now lists them with the controls that work, plus the git traps of the night: branch after the fork sync, check ls-remote for a stale branch, prefer a plain shallow clone over a partial one, and space the code searches.
grow-my-repo gets the browser facts for sites that need a real session or a person in front of a challenge (DeepWiki, cursor.directory) and two form quirks.
Codex copies rebuilt with scripts/build_codex.py; validate_skills.py passes with no warnings.
Summary by CodeRabbit