القائمة
Repo hygiene rules for Latitude. Prevents generated/extracted artifacts from entering commits, release branches, tags, or jars. Provides the canonical ignore list and cleanup commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Read-only analyzer for Latitude atlas and headless proof artifacts. Use when you have atlas or report outputs and need a structured audit of what looks wrong, what category of wrong it is, and whether the evidence suggests real worldgen regression versus validator or viewer/report drift. Do not use for rerunning jobs, rebuilding, file modification, or multi-fix brainstorming.
Read-only Git diff explainer for changelogs, PR summaries, slice review, and scope checks. Use when you need plain-English explanations of working tree diffs, staged diffs, or comparisons between two refs, with subsystem grouping and risk/scope assessment. Do not use for commit, tag, push, stash, checkout, rebase, reset, or file modification.
Read-only triage assistant for worldgen and system regressions. Use when a symptom needs to be mapped to the most likely pipeline stage and reduced to exactly one narrow next slice, especially for biome placement, seams, atlas output, or unclear bug location. Do not use for code changes, multi-fix brainstorming, or broad debugging spirals.
Read-only pre-flight guard before using the savepoint skill. Use when deciding whether the current Git repo is safe and narrow enough for a one-slice savepoint, with a clear safe-or-stop decision based on repo root, branch, HEAD, staged and unstaged changes, and generated junk. Do not use for commit/tag/push, stash, reset, cleanup, branch surgery, or conflict resolution.
Create Git savepoints after a successful change: show status, interactively stage intended hunks, commit with a concise slice summary, tag as save/slug, push commit and tag, then report branch+hash+tag. Use when you need a fast rollback point or to checkpoint a completed slice.
Read-only workspace hygiene checker for Git repos. Use when repo state feels cluttered, before handoff, savepoint, or release hygiene, or when you need to distinguish runtime junk, generated files, temp world files, and machine-specific clutter from real source edits. Do not use for deletion, git clean, reset, stash automation, or .gitignore edits.
| name | latitude-repo-hygiene |
| description | Repo hygiene rules for Latitude. Prevents generated/extracted artifacts from entering commits, release branches, tags, or jars. Provides the canonical ignore list and cleanup commands. |
This skill prevents:
These must never be committed to any release branch (and should generally be ignored everywhere):
_mcsrc_extract/run/ (worlds, logs, caches)logs/.gradle/.gradle-user-home/build/out/.idea/.vscode/.classpath.project.settings/*.imlTooling:
.windsurf/ (skills, internal state) — never ship inside jarsprocessedMods/ cache folder under run/.fabric/OS noise:
Thumbs.db.DS_StoreIf any of these appear in git status, STOP and fix before continuing.
maincompat/1.21.1feature/* branches, especially if they contain any forbidden folders.The repo must include ignore rules for every “never-commit folder” above.
If the assistant proposes adding a generated folder to the repo, it must justify why and confirm it is safe for release.
Remove-Item -Recurse -Force .\build -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force .\.gradle -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force .\.gradle-user-home -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force .\run\.fabric\processedMods\* -ErrorAction SilentlyContinue
git restore --staged .
git restore .
Preferred fix:
Always check the jar you will upload:
jar tf .\build\libs\<YOUR_JAR_NAME>.jar | findstr /I "_mcsrc_extract .windsurf SKILL.md com/mojang blaze3d"
Pass criteria:
The assistant must:
.gitignore prevents recurrence