bump-kajson
Skill950 starsChanged 8 months agoLicence not identifiedView on GitHub
Move this repo's exact `kajson` dependency pin to the latest release on PyPI (or a version you name), re-lock, adapt the engine to whatever the new release changed, retire any workaround the release makes unnecessary, run the checks, and write the CHANGELOG entry — stopping before the commit. Use whenever the user says "bump kajson", "update kajson", "upgrade kajson", "move to kajson 0.8.0", "get us on the latest kajson", "is our kajson pin stale", "what's the latest kajson", or asks to build against a newly published `kajson` release. Also use when a failure smells like a kajson version mismatch — a `KajsonDecoderError` or `UnijsonEncoderError` on a payload that used to round-trip, a `ClassRegistryNotFoundError` after an upstream change, a pyright `reportAttributeAccessIssue` on something under `kajson.`, or a `uv lock` reporting kajson unsatisfiable. This is the **`kajson` PyPI package** (the universal JSON encoder/decoder from the sibling `kajson` repo, which is the serialization layer this engine is built on) — not releasing kajson itself, which belongs in that repo, and not releasing pipelex, which is the `release` skill.
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-migrationSkill
- add-modelSkill
- bump-mthdsSkill
- drift-reviewSkill
- releaseSkill
- test-modelSkill
- update-graph-uiSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.