kit-ci-triage
Skill0 starsChanged 16 days agoMITView on GitHub
Get build and test proof for Kit and diagnose CI failures, especially when working on Windows. Use before claiming a Kit change works, when a check fails on a PR, or when a local cargo build behaves oddly on Windows.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- using-agent-skillsSkill
- kit-evalsSkill
- kit-provider-adaptersSkill
- kit-releaseSkill
- kit-tuiSkill
- a11y-passSkill
- add-readmeSkill
- api-docsSkill
- changelogSkill
- cli-helpSkill
- code-reviewSkill
- completeness-qaSkill
- data-checkSkill
- deps-hygieneSkill
- fix-bugSkill
- project-setupSkill
- pr-readySkill
- ship-checklistSkill
- workspace-setupSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Encoding: read and write text as UTF-8 explicitly (encoding="utf-8" in Python).
- Distinctive: line 40
Add or fix the test that would have caught it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Kit CI triage
Where proof comes from
| Check | Workflow / job | Runs on | Proves |
fmt, clippy -D warnings, cargo test --workspace | rust.yml → quality | ubuntu, macos, windows | every crate, the TUI snapshots, the CLI integration tests |
| Packaging | rust.yml → crates.io package | ubuntu | cargo package --workspace --locked; version copies agree |
| Cold start | rust.yml → startup budget | ubuntu, windows | kit --version mean under 100 ms (hyperfine) |
| npm launcher | rust.yml → npm package (scripts/npm-smoke.mjs) | 3 OSes | the packed tarballs install and kit runs through the shim |
| Installers | installers.yml | 3 OSes | install.sh / install.ps1 against a local release |
rust.yml is path-filtered: a docs-only PR runs no Rust checks. That is not a pass for code; it means
there was no code. Read results with gh pr checks <n> -R Zwin-ux/kit and
gh run view <run-id> -R Zwin-ux/kit --log-failed. Use the app's PR status tools rather than polling.
Say which rows ran and on which OS before calling anything verified.
Known traps
- Windows path length: a checkout in a deep folder makes
link.exefail withLNK1104: cannot open file … build_script_build-….exe. SetCARGO_TARGET_DIRto a short folder (Git Bash:export CARGO_TARGET_DIR=C:/kit-target; PowerShell:$env:CARGO_TARGET_DIR = 'C:\kit-target'). NoDefaultCurrentDirectoryInExePath=1(set on the owner's hardened machine):cmd /C name.cmdno longer findsname.cmdin the current folder. Tests and checks must write.\name.cmd.- CRLF:
core.autocrlf=truechecks files out with\r\n. Strip\rbefore grepping, and assert the count of any scripted replacement. Insta snapshots compare with line endings normalised. - Insta: a changed screen writes
.snap.newand fails. RunINSTA_UPDATE=always cargo test -p kitctl-tui(PowerShell:$env:INSTA_UPDATE = 'always'; cargo test -p kitctl-tui) only after reading the diff, then commit the.snapand readgit diffof it line by line. - Clippy on newer stable: CI uses
dtolnay/rust-toolchain@stable, which can be newer than your local toolchain. A lint that only CI reports is real; fix it, don't pin the toolchain down. - Encoding: read and write text as UTF-8 explicitly (
encoding="utf-8"in Python).©,·,→and box-drawing characters appear in Kit's output and docs.
Failure loop
- Find the failing job and the first real error line, not the summary.
- Reproduce locally if the toolchain allows; otherwise reason from the log and push a fix to the PR branch.
- Add or fix the test that would have caught it.
- Push and read the new run on every OS before saying it is fixed.
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.

