[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BNFPWH6CKGXRN5X078H367":3,"skill-same:01M7BNFPWH6CKGXRN5X078H367":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},"01M7BNFPWH6CKGXRN5X078H367","maven-build-lifecycle",null,"Use when reproducing and repairing Maven CI build failures, especially legacy multi-module builds and Maven Invoker integration tests.","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-all\u002Frepaired_skill\u002Fmaven-build-lifecycle\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maven-build-lifecycle\ndescription: Use when reproducing and repairing Maven CI build failures, especially legacy multi-module builds and Maven Invoker integration tests.\n---\n\n# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nThe failed repository lives at `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>` (for\nexample `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Fgoogle\u002Fauto\u002F\u003Cid>`). Always use the\n`\u003Crepo>\u002F\u003Cid>` placeholders — never hardcode a single project path.\n\nBefore finishing:\n\n1. Write a diagnosis note to `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`\n   recording: failing module path, failing goal, exact error excerpt, root\n   cause classification (code vs. configuration), and the planned fix list\n   (file → change). This file is the scratchpad for the patch step.\n2. Create at least one non-empty standard unified diff at\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (and `patch_2.diff`,\n   `patch_3.diff`, … if more than one concern) containing the intended\n   source\u002Fconfiguration change. Use `diff --git a\u002F… b\u002F…` headers so\n   `git apply` accepts them.\n3. Apply the patch(es) inside the repository, e.g.\n   `cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid> && git apply --whitespace=nowarn patch_1.diff`.\n   Fall back to `patch -p1 \u003C patch_1.diff` if the directory is not a git\n   working tree.\n4. Check `git diff` \u002F `git status` and ensure the intended project file —\n   not only the patch artifact — was changed, then re-run the reproduction\n   command to confirm the fix.\n\n## Minimal diagnostic sequence\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# 1. Inspect toolchain & module layout\ncat .travis.yml 2>\u002Fdev\u002Fnull | sed -n '1,80p'\nsed -n '1,120p' pom.xml\ngrep -nE '\u003Cmodule>|\u003Cjava.version>|maven.compiler|requireJavaVersion' -r . --include=pom.xml | head -n 50\n\n# 2. Reproduce the full build failure (continue past first error, verbose)\nmvn -B -ntp -fae -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# 3. Narrow to the failing module once identified\nmvn -B -ntp -e -pl \u003Cfailing-module> -am verify 2>&1 | tee \u002Ftmp\u002Fbuild-module.log\n\n# 4. For Invoker \u002F nested test projects, re-run inside the nested pom\n(cd src\u002Fit\u002F\u003Cnested-project> && mvn -B -ntp -e verify) 2>&1 | tee \u002Ftmp\u002Fbuild-nested.log\n\n# 5. Enumerate error signatures for the iterate-match-act loop\ngrep -nE '\\b(ERROR|BUILD FAILURE|cannot find symbol|package .* does not exist|Could not resolve)\\b' \u002Ftmp\u002Fbuild.log | head -n 40\n```\n\n## Toolchain selection\n\n- Detect the required JDK first: check `.travis.yml` (`jdk:` list),\n  root `pom.xml` for `maven.compiler.release` \u002F `source` \u002F `target`,\n  and any `maven-enforcer-plugin` `requireJavaVersion` rule.\n- Align the invoked JDK with the strictest constraint. If the repo pins\n  Java 8 but `JAVA_HOME` points elsewhere, export the matching JDK before\n  invoking Maven (`export JAVA_HOME=…; export PATH=$JAVA_HOME\u002Fbin:$PATH`).\n- Prefer `maven.compiler.release` over separate `source`\u002F`target` when\n  editing modern builds; preserve the existing style when editing legacy\n  builds to avoid cascading enforcer failures.\n- If a `toolchains.xml` is referenced, do not introduce new JDK vendors —\n  reuse what the environment provides.\n- Keep the Maven version compatible with the repo: very old projects may\n  require Maven 3.6.x behaviour (e.g. legacy `http` repositories); do not\n  upgrade plugin versions beyond what the pinned Maven supports.\n\n## Nested test projects & Invoker ITs\n\n- Enumerate submodules via the parent `\u003Cmodules>` block; nested test\n  fixtures also live under `src\u002Fit\u002F\u003Cproject>\u002Fpom.xml` (Maven Invoker) or\n  `src\u002Ftest\u002Fresources\u002Fprojects\u002F…`.\n- Nested poms often inherit versions from the parent `dependencyManagement`.\n  Before adding a `\u003Cversion>` to a nested dependency, check whether the\n  parent already manages it — prefer fixing the parent once over editing\n  every nested pom.\n- Constrain edits to the failing nested module. Do not touch unrelated\n  sibling modules or sample projects just because they share a parent.\n- When reproducing, use `-pl \u003Cmodule> -am` to build only the failing path\n  plus its upstream dependencies; use `-amd` only when you need to verify\n  downstream consumers.\n- For Invoker ITs, reproduce by running the invoker goal\n  (`mvn -B -ntp -e invoker:run`) or by `cd`-ing into the nested project\n  and running its own `mvn verify` — but keep patches scoped to the files\n  the IT actually exercises.\n- If a nested project uses annotation processors (AutoValue, AutoService,\n  Dagger), prefer `maven-compiler-plugin`'s `\u003CannotationProcessorPaths>`\n  over `provided` scope so the processor jar is not shipped.\n\n## General Maven lifecycle reminders\n\n- Lifecycle phase order (default): `validate → compile → test → package →\n  verify → install → deploy`. `clean` is a separate lifecycle; `site` too.\n  Binding a plugin to the wrong phase is a common cause of \"works locally,\n  fails in CI\" drift.\n- `-fae` (fail at end) surfaces every failing module in one run — prefer it\n  while diagnosing. Switch to `-ff` (fail fast) once you expect success.\n- Use `-o` (offline) only after at least one successful online resolve;\n  otherwise missing artifacts masquerade as code errors.\n- `-pl \u003Cmodule>` restricts the reactor; combine with `-am` (also make\n  upstream) or `-amd` (also make downstream) to keep the build minimal\n  while still exercising real dependency wiring.\n- `-B -ntp -e` is the standard CI triple: batch mode, no transfer progress,\n  show stack traces. Always include them when capturing logs for the\n  diagnosis note.\n- Prefer `mvn help:effective-pom -pl \u003Cmodule>` to resolve where a version\n  or plugin configuration actually comes from before editing.\n- Keep edits minimal and justified by an observed error; every change in\n  a patch should map back to a line in `failed_reasons.txt`.\n","# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nThe failed repository lives at `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>` (for\nexample `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Fgoogle\u002Fauto\u002F\u003Cid>`). Always use the\n`\u003Crepo>\u002F\u003Cid>` placeholders — never hardcode a single project path.\n\nBefore finishing:\n\n1. Write a diagnosis note to `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`\n   recording: failing module path, failing goal, exact error excerpt, root\n   cause classification (code vs. configuration), and the planned fix list\n   (file → change). This file is the scratchpad for the patch step.\n2. Create at least one non-empty standard unified diff at\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff` (and `patch_2.diff`,\n   `patch_3.diff`, … if more than one concern) containing the intended\n   source\u002Fconfiguration change. Use `diff --git a\u002F… b\u002F…` headers so\n   `git apply` accepts them.\n3. Apply the patch(es) inside the repository, e.g.\n   `cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid> && git apply --whitespace=nowarn patch_1.diff`.\n   Fall back to `patch -p1 \u003C patch_1.diff` if the directory is not a git\n   working tree.\n4. Check `git diff` \u002F `git status` and ensure the intended project file —\n   not only the patch artifact — was changed, then re-run the reproduction\n   command to confirm the fix.\n\n## Minimal diagnostic sequence\n\n```bash\ncd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\n\n# 1. Inspect toolchain & module layout\ncat .travis.yml 2>\u002Fdev\u002Fnull | sed -n '1,80p'\nsed -n '1,120p' pom.xml\ngrep -nE '\u003Cmodule>|\u003Cjava.version>|maven.compiler|requireJavaVersion' -r . --include=pom.xml | head -n 50\n\n# 2. Reproduce the full build failure (continue past first error, verbose)\nmvn -B -ntp -fae -e clean verify 2>&1 | tee \u002Ftmp\u002Fbuild.log\n\n# 3. Narrow to the failing module once identified\nmvn -B -ntp -e -pl \u003Cfailing-module> -am verify 2>&1 | tee \u002Ftmp\u002Fbuild-module.log\n\n# 4. For Invoker \u002F nested test projects, re-run inside the nested pom\n(cd src\u002Fit\u002F\u003Cnested-project> && mvn -B -ntp -e verify) 2>&1 | tee \u002Ftmp\u002Fbuild-nested.log\n\n# 5. Enumerate error signatures for the iterate-match-act loop\ngrep -nE '\\b(ERROR|BUILD FAILURE|cannot find symbol|package .* does not exist|Could not resolve)\\b' \u002Ftmp\u002Fbuild.log | head -n 40\n```\n\n## Toolchain selection\n\n- Detect the required JDK first: check `.travis.yml` (`jdk:` list),\n  root `pom.xml` for `maven.compiler.release` \u002F `source` \u002F `target`,\n  and any `maven-enforcer-plugin` `requireJavaVersion` rule.\n- Align the invoked JDK with the strictest constraint. If the repo pins\n  Java 8 but `JAVA_HOME` points elsewhere, export the matching JDK before\n  invoking Maven (`export JAVA_HOME=…; export PATH=$JAVA_HOME\u002Fbin:$PATH`).\n- Prefer `maven.compiler.release` over separate `source`\u002F`target` when\n  editing modern builds; preserve the existing style when editing legacy\n  builds to avoid cascading enforcer failures.\n- If a `toolchains.xml` is referenced, do not introduce new JDK vendors —\n  reuse what the environment provides.\n- Keep the Maven version compatible with the repo: very old projects may\n  require Maven 3.6.x behaviour (e.g. legacy `http` repositories); do not\n  upgrade plugin versions beyond what the pinned Maven supports.\n\n## Nested test projects & Invoker ITs\n\n- Enumerate submodules via the parent `\u003Cmodules>` block; nested test\n  fixtures also live under `src\u002Fit\u002F\u003Cproject>\u002Fpom.xml` (Maven Invoker) or\n  `src\u002Ftest\u002Fresources\u002Fprojects\u002F…`.\n- Nested poms often inherit versions from the parent `dependencyManagement`.\n  Before adding a `\u003Cversion>` to a nested dependency, check whether the\n  parent already manages it — prefer fixing the parent once over editing\n  every nested pom.\n- Constrain edits to the failing nested module. Do not touch unrelated\n  sibling modules or sample projects just because they share a parent.\n- When reproducing, use `-pl \u003Cmodule> -am` to build only the failing path\n  plus its upstream dependencies; use `-amd` only when you need to verify\n  downstream consumers.\n- For Invoker ITs, reproduce by running the invoker goal\n  (`mvn -B -ntp -e invoker:run`) or by `cd`-ing into the nested project\n  and running its own `mvn verify` — but keep patches scoped to the files\n  the IT actually exercises.\n- If a nested project uses annotation processors (AutoValue, AutoService,\n  Dagger), prefer `maven-compiler-plugin`'s `\u003CannotationProcessorPaths>`\n  over `provided` scope so the processor jar is not shipped.\n\n## General Maven lifecycle reminders\n\n- Lifecycle phase order (default): `validate → compile → test → package →\n  verify → install → deploy`. `clean` is a separate lifecycle; `site` too.\n  Binding a plugin to the wrong phase is a common cause of \"works locally,\n  fails in CI\" drift.\n- `-fae` (fail at end) surfaces every failing module in one run — prefer it\n  while diagnosing. Switch to `-ff` (fail fast) once you expect success.\n- Use `-o` (offline) only after at least one successful online resolve;\n  otherwise missing artifacts masquerade as code errors.\n- `-pl \u003Cmodule>` restricts the reactor; combine with `-am` (also make\n  upstream) or `-amd` (also make downstream) to keep the build minimal\n  while still exercising real dependency wiring.\n- `-B -ntp -e` is the standard CI triple: batch mode, no transfer progress,\n  show stack traces. Always include them when capturing logs for the\n  diagnosis note.\n- Prefer `mvn help:effective-pom -pl \u003Cmodule>` to resolve where a version\n  or plugin configuration actually comes from before editing.\n- Keep edits minimal and justified by an observed error; every change in\n  a patch should map back to a line in `failed_reasons.txt`.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-all\u002Frepaired_skill\u002Fmaven-build-lifecycle",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 maven-build-lifecycle",{"tool":37,"command":38},"bunx","bunx skills add linyouxue\u002Fskill-repair-benchmark --skill maven-build-lifecycle",{"tool":40,"command":41},"pnpm","pnpm dlx skills add linyouxue\u002Fskill-repair-benchmark --skill maven-build-lifecycle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fcontrolled-skill-repair-experiments\u002Fresult\u002Fskilltta-claude4.7\u002Ftasks\u002Fsingle-fix-build-google-auto-all\u002Frepaired_skill\u002Fmaven-build-lifecycle\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",[],[]]