[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BNF2MABFP4QQJ8HBDHVQ7P":3,"skill-same:01M7BNF2MABFP4QQJ8HBDHVQ7P":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BNF2MABFP4QQJ8HBDHVQ7P","skilltta-task-guidance",null,"Temporary task guidance for diagnosing and fixing a failing Java\u002FMaven build in \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>, producing analysis notes, diff patches, and applying them.","linyouxue\u002Fskill-repair-benchmark","linyouxue","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F216151464?v=4","01M7BJEVCXKD74KH6FG9CBVSQB","林宥学","01M7BJEVE02NP217V93BKZFC0J",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fcontrolled-skill-repair-experiments\u002Fresult\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-RI-001\u002Frepaired_skill\u002Fskilltta-task-guidance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skilltta-task-guidance\ndescription: Temporary task guidance for diagnosing and fixing a failing Java\u002FMaven build in \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>, producing analysis notes, diff patches, and applying them.\n---\n\n# SkillTTA Task Guidance: Fix Java Maven Build Failure\n\n## Objective\nRepair a broken Java build located at `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>` by:\n1. Diagnosing the failure (code vs. build config).\n2. Writing analysis to `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`.\n3. Emitting standard unified diff patches as `patch_{i}.diff` in the repo root.\n4. Applying the patches to the working tree.\n\n## Location Hint Interpretation\nThe hint points at `maven-build-lifecycle\u002FSKILL.md` conventions regarding:\n- **Toolchain selection** (JDK version, Maven version).\n- **Failure reproduction** (how to invoke the build locally).\n- **Build command conventions** (e.g., `mvn -B -V -ntp ...`).\nTreat these as *process* guidance — the actual bug likely lies in `pom.xml` (plugin\u002Fdep versions, Java source\u002Ftarget, repository config) or in a source file that no longer compiles under the configured JDK. Do not blindly trust the hint; verify by reading the repo.\n\n## Step 1 — Reconnaissance (apply retrieval-style directory walking)\nMirror the pattern from the retrieved examples where files are enumerated and filtered by regex:\n- `ls` and `find` the repo root; locate `pom.xml` (and any child modules).\n- Enumerate `src\u002Fmain\u002Fjava` and `src\u002Ftest\u002Fjava` for Java sources.\n- Grep for suspicious markers: `TODO`, `@Override`, deprecated APIs, `javax.*` vs `jakarta.*`, missing imports.\n- Inspect `.travis.yml` \u002F `.github\u002Fworkflows\u002F*` if present to learn the intended JDK and Maven invocation.\n\nReproduce the failure:\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\nmvn -B -V -ntp -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n```\nIf `verify` is too heavy, fall back to `compile` then `test-compile`.\n\n## Step 2 — Classify the Error\nFrom `\u002Ftmp\u002Fbuild.log`, categorize:\n- **Compilation error** → fix Java source (missing symbol, type mismatch, generics, annotation processor).\n- **Plugin\u002Fdep resolution error** → fix `pom.xml` (version pin, repository, relocated groupId like `com.google.auto.value`).\n- **Toolchain mismatch** → align `maven.compiler.source\u002Ftarget` or `release` with available JDK.\n- **Enforcer \u002F checkstyle \u002F animal-sniffer** → either fix the offending code or relax the rule if clearly misconfigured.\n\nFor a `google-auto`-flavored repo (per trial id), common culprits:\n- `auto-value` \u002F `auto-service` annotation processor not registered under `\u003CannotationProcessorPaths>` in `maven-compiler-plugin`.\n- Generated `AutoValue_*` classes missing because processor path is absent.\n- Mismatch between `auto-value-annotations` (compile) and `auto-value` (processor only).\n\n## Step 3 — Write Analysis Notes\nWrite `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` with:\n- Exact failing Maven goal and first error excerpt.\n- Root cause hypothesis.\n- Ordered list of file-level fixes planned.\n- Validation command.\n\n## Step 4 — Produce Diffs\nFor each logical change, write `patch_{i}.diff` at repo root in unified `git diff` format:\n```\ndiff --git a\u002Fpom.xml b\u002Fpom.xml\n--- a\u002Fpom.xml\n+++ b\u002Fpom.xml\n@@ ...\n```\nKeep patches minimal and focused (one concern per file). Prefer:\n- Adjusting `pom.xml` plugin\u002Fdependency declarations.\n- Adding missing imports or `@Override` corrections in Java sources.\n- Pinning versions rather than removing dependencies.\n\n## Step 5 — Apply Patches\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\nfor p in patch_*.diff; do\n  git apply --whitespace=nowarn \"$p\" || patch -p1 \u003C \"$p\"\ndone\n```\nThen re-run the build command and confirm success (or iterate).\n\n## Transferable Patterns from Retrieved Examples\nAlthough the retrieved examples are Python file-manipulation tasks, their reusable *patterns* are:\n- **Enumerate-then-filter** (`os.listdir` + regex): mirror via `find ... | grep` to locate pom files and offending sources.\n- **Guard preconditions** (`os.path.exists`, `makedirs`): before applying patches, confirm the target files exist; before writing `failed_reasons.txt`, ensure the parent dir exists.\n- **Idempotent move\u002Fwrite**: ensure patches are safe to re-apply (check with `git apply --check` first).\n- **Explicit count \u002F status return**: after applying, report number of patches applied and the final build status.\n\n## Deliverables Checklist\n- [ ] `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` populated.\n- [ ] One or more `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_{i}.diff` files.\n- [ ] Patches applied cleanly to the repo.\n- [ ] Build command rerun demonstrates progress past the original error.\n","# SkillTTA Task Guidance: Fix Java Maven Build Failure\n\n## Objective\nRepair a broken Java build located at `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>` by:\n1. Diagnosing the failure (code vs. build config).\n2. Writing analysis to `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`.\n3. Emitting standard unified diff patches as `patch_{i}.diff` in the repo root.\n4. Applying the patches to the working tree.\n\n## Location Hint Interpretation\nThe hint points at `maven-build-lifecycle\u002FSKILL.md` conventions regarding:\n- **Toolchain selection** (JDK version, Maven version).\n- **Failure reproduction** (how to invoke the build locally).\n- **Build command conventions** (e.g., `mvn -B -V -ntp ...`).\nTreat these as *process* guidance — the actual bug likely lies in `pom.xml` (plugin\u002Fdep versions, Java source\u002Ftarget, repository config) or in a source file that no longer compiles under the configured JDK. Do not blindly trust the hint; verify by reading the repo.\n\n## Step 1 — Reconnaissance (apply retrieval-style directory walking)\nMirror the pattern from the retrieved examples where files are enumerated and filtered by regex:\n- `ls` and `find` the repo root; locate `pom.xml` (and any child modules).\n- Enumerate `src\u002Fmain\u002Fjava` and `src\u002Ftest\u002Fjava` for Java sources.\n- Grep for suspicious markers: `TODO`, `@Override`, deprecated APIs, `javax.*` vs `jakarta.*`, missing imports.\n- Inspect `.travis.yml` \u002F `.github\u002Fworkflows\u002F*` if present to learn the intended JDK and Maven invocation.\n\nReproduce the failure:\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\nmvn -B -V -ntp -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n```\nIf `verify` is too heavy, fall back to `compile` then `test-compile`.\n\n## Step 2 — Classify the Error\nFrom `\u002Ftmp\u002Fbuild.log`, categorize:\n- **Compilation error** → fix Java source (missing symbol, type mismatch, generics, annotation processor).\n- **Plugin\u002Fdep resolution error** → fix `pom.xml` (version pin, repository, relocated groupId like `com.google.auto.value`).\n- **Toolchain mismatch** → align `maven.compiler.source\u002Ftarget` or `release` with available JDK.\n- **Enforcer \u002F checkstyle \u002F animal-sniffer** → either fix the offending code or relax the rule if clearly misconfigured.\n\nFor a `google-auto`-flavored repo (per trial id), common culprits:\n- `auto-value` \u002F `auto-service` annotation processor not registered under `\u003CannotationProcessorPaths>` in `maven-compiler-plugin`.\n- Generated `AutoValue_*` classes missing because processor path is absent.\n- Mismatch between `auto-value-annotations` (compile) and `auto-value` (processor only).\n\n## Step 3 — Write Analysis Notes\nWrite `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` with:\n- Exact failing Maven goal and first error excerpt.\n- Root cause hypothesis.\n- Ordered list of file-level fixes planned.\n- Validation command.\n\n## Step 4 — Produce Diffs\nFor each logical change, write `patch_{i}.diff` at repo root in unified `git diff` format:\n```\ndiff --git a\u002Fpom.xml b\u002Fpom.xml\n--- a\u002Fpom.xml\n+++ b\u002Fpom.xml\n@@ ...\n```\nKeep patches minimal and focused (one concern per file). Prefer:\n- Adjusting `pom.xml` plugin\u002Fdependency declarations.\n- Adding missing imports or `@Override` corrections in Java sources.\n- Pinning versions rather than removing dependencies.\n\n## Step 5 — Apply Patches\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\nfor p in patch_*.diff; do\n  git apply --whitespace=nowarn \"$p\" || patch -p1 \u003C \"$p\"\ndone\n```\nThen re-run the build command and confirm success (or iterate).\n\n## Transferable Patterns from Retrieved Examples\nAlthough the retrieved examples are Python file-manipulation tasks, their reusable *patterns* are:\n- **Enumerate-then-filter** (`os.listdir` + regex): mirror via `find ... | grep` to locate pom files and offending sources.\n- **Guard preconditions** (`os.path.exists`, `makedirs`): before applying patches, confirm the target files exist; before writing `failed_reasons.txt`, ensure the parent dir exists.\n- **Idempotent move\u002Fwrite**: ensure patches are safe to re-apply (check with `git apply --check` first).\n- **Explicit count \u002F status return**: after applying, report number of patches applied and the final build status.\n\n## Deliverables Checklist\n- [ ] `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` populated.\n- [ ] One or more `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_{i}.diff` files.\n- [ ] Patches applied cleanly to the repo.\n- [ ] Build command rerun demonstrates progress past the original error.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-RI-001\u002Frepaired_skill\u002Fskilltta-task-guidance",1,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark","https:\u002F\u002Fgithub.com\u002Flinyouxue","2026-11-14 20:28:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add linyouxue\u002Fskill-repair-benchmark --skill skilltta-task-guidance",{"tool":37,"command":38},"bunx","bunx skills add linyouxue\u002Fskill-repair-benchmark --skill skilltta-task-guidance",{"tool":40,"command":41},"pnpm","pnpm dlx skills add linyouxue\u002Fskill-repair-benchmark --skill skilltta-task-guidance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fcontrolled-skill-repair-experiments\u002Fresult\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-RI-001\u002Frepaired_skill\u002Fskilltta-task-guidance\u002FSKILL.md",true,[],[46,53,60,67,72,77],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7E1HGVRY73NBJ022CJG13X6","video-frame-extraction","Extract frames from video files and save them as images using OpenCV","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7E1HAG5R7CJ9C8NYJS771MB","openai-vision","Analyze images and multi-frame sequences using OpenAI GPT vision models","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7E1H7DADKB6QBWKC2KQ63SZ","image-ocr","Extract text content from images using Tesseract OCR via Python, including structured field extraction from receipts and forms","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[],{"skillNo":68,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7E1H0WBNT43TENGQY7AVZHD","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":73,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7E1GTC7D4N4Q2EF03875J9E","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":78,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E1GQ92CWFMGH53KSSE4WER","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[]]