[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJSWR0AASAE4S6GYS7995S":3,"skill-same:01M7BJSWR0AASAE4S6GYS7995S":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},"01M7BJSWR0AASAE4S6GYS7995S","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\u002Fmmg2skill-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-3\u002Fskills\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## Steps\n1. **Locate the real checkout workspace** under `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F**` (do not stop at a namespace\u002Fowner folder; you must reach the final build workspace that contains `pom.xml` and usually a `.git` directory\u002Ffile).\n   - Start with discovery (single tool calls; a short `cd ... && ls -la` is OK):\n     ```bash\n     cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed && ls -la\n     ```\n   - Drill down with `ls -la` until you reach the directory that actually contains the build files.\n   - If you’re unsure where the checkout root is, find it directly:\n     ```bash\n     find \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed -maxdepth 5 -type d -name .git -print\n     ```\n     Then `cd` to the parent directory of the `.git` hit and confirm:\n     ```bash\n     pwd\n     ```\n     ```bash\n     ls -la\n     ```\n     (You should see `pom.xml`, `.travis.yml`, `mvnw`, or module directories.)\n\n2. **Read CI configuration before interpreting errors** to learn the real Maven command and JDK:\n   ```bash\n   sed -n '1,220p' .travis.yml\n   ```\n\n3. **Record toolchain versions** (paste these into `failed_reasons.txt`):\n   ```bash\n   java -version\n   ```\n   ```bash\n   javac -version\n   ```\n   ```bash\n   mvn -version\n   ```\n\n4. **Match the CI JDK before patching project files.** If CI pins an older JDK and the environment provides the BugSwarm\u002FTravis switcher:\n   ```bash\n   source \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\n   ```\n   ```bash\n   jdk_switcher use \u003Cci-jdk>\n   ```\n   ```bash\n   export TRAVIS_JDK_VERSION=\u003Cci-jdk>\n   ```\n   ```bash\n   java -version\n   ```\n   Do not “modernize away” failures that only occur because you ran the project on a newer JDK than CI.\n\n5. **Reproduce the failure using the CI command** (same flags\u002Fprofiles, including any `-f \u003Creactor-pom>`). If you need clearer “missing artifact\u002Fplugin” coordinates, also try:\n   ```bash\n   mvn -o -B -e verify --fail-at-end\n   ```\n\n6. **Write\u002Fupdate the required diagnosis + plan file early** (don’t defer; keep updating as you learn more):\n   ```bash\n   printf '%s\\n' \\\n     \"Repo: $(pwd)\" \\\n     \"Repro command: \u003Cpaste exact mvn command from CI>\" \\\n     \"Observed failure: \u003Cpaste key Maven error lines>\" \\\n     \"Root cause guess: \u003Ccode vs build config?>\" \\\n     \"Plan: \u003Cfiles to change + why>\" \\\n     > \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt\n   ```\n   Verify it exists and is non-empty:\n   ```bash\n   test -s \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt && echo \"notes ok\"\n   ```\n\n7. **Maven Invoker \u002F nested test projects: fix dependency resolution in the template sources, not `target\u002F**`.**\n   - If the failure is in a nested build (Invoker often runs under `target\u002Fit\u002F**` or `target\u002F**`), map the failing nested directory back to its **source template** (commonly `src\u002Fit\u002F**`, sometimes `src\u002Ftest\u002Fresources\u002F**`) and edit that template’s `pom.xml` \u002F `invoker.properties`, not generated copies under `target\u002F**`.\n   - Choose the correct modification scope by checking the nested project’s `\u003Cparent>` chain:\n     - If the nested project **does not inherit** from your reactor\u002Fparent POM, fixes must be made **inside the nested template** (or a parent POM within that template), because it won’t see your reactor `dependencyManagement\u002FpluginManagement`.\n     - If it **does inherit** from a repository parent POM, fix the parent so the nested project picks up the change naturally.\n   - Distinguish **plugin resolution** failures vs normal dependency failures; nested builds may need their own plugin versions\u002Frepositories when they don’t inherit yours.\n\n8. **Create the required patch diff file(s), then apply them to the repo.**\n   - Generate a unified diff from local edits (run in the repo root so the patch lands at `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff`):\n     ```bash\n     git diff > patch_1.diff\n     ```\n     ```bash\n     test -s patch_1.diff && echo \"patch ok\"\n     ```\n   - Prove\u002Fapply the patch artifact (separates “patch creation” from “patch application”):\n     ```bash\n     git checkout -- .\n     ```\n     ```bash\n     git apply patch_1.diff\n     ```\n   - Verify the working tree reflects the patch:\n     ```bash\n     git status\n     ```\n     ```bash\n     git diff --stat\n     ```\n\n9. **Re-run the exact CI verification command until it succeeds**, remembering `mvn verify` may run integration\u002FInvoker steps that `mvn test` does not.\n\n## Expected Result\n- You are working inside the concrete checkout directory (contains `pom.xml` and typically `.git`).\n- `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` exists and is non-empty.\n- `patch_1.diff` exists in the repo root and is non-empty.\n- The Maven CI command (including nested\u002FInvoker builds when present) passes under the CI-declared JDK.\n","## Steps\n1. **Locate the real checkout workspace** under `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F**` (do not stop at a namespace\u002Fowner folder; you must reach the final build workspace that contains `pom.xml` and usually a `.git` directory\u002Ffile).\n   - Start with discovery (single tool calls; a short `cd ... && ls -la` is OK):\n     ```bash\n     cd \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed && ls -la\n     ```\n   - Drill down with `ls -la` until you reach the directory that actually contains the build files.\n   - If you’re unsure where the checkout root is, find it directly:\n     ```bash\n     find \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed -maxdepth 5 -type d -name .git -print\n     ```\n     Then `cd` to the parent directory of the `.git` hit and confirm:\n     ```bash\n     pwd\n     ```\n     ```bash\n     ls -la\n     ```\n     (You should see `pom.xml`, `.travis.yml`, `mvnw`, or module directories.)\n\n2. **Read CI configuration before interpreting errors** to learn the real Maven command and JDK:\n   ```bash\n   sed -n '1,220p' .travis.yml\n   ```\n\n3. **Record toolchain versions** (paste these into `failed_reasons.txt`):\n   ```bash\n   java -version\n   ```\n   ```bash\n   javac -version\n   ```\n   ```bash\n   mvn -version\n   ```\n\n4. **Match the CI JDK before patching project files.** If CI pins an older JDK and the environment provides the BugSwarm\u002FTravis switcher:\n   ```bash\n   source \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\n   ```\n   ```bash\n   jdk_switcher use \u003Cci-jdk>\n   ```\n   ```bash\n   export TRAVIS_JDK_VERSION=\u003Cci-jdk>\n   ```\n   ```bash\n   java -version\n   ```\n   Do not “modernize away” failures that only occur because you ran the project on a newer JDK than CI.\n\n5. **Reproduce the failure using the CI command** (same flags\u002Fprofiles, including any `-f \u003Creactor-pom>`). If you need clearer “missing artifact\u002Fplugin” coordinates, also try:\n   ```bash\n   mvn -o -B -e verify --fail-at-end\n   ```\n\n6. **Write\u002Fupdate the required diagnosis + plan file early** (don’t defer; keep updating as you learn more):\n   ```bash\n   printf '%s\\n' \\\n     \"Repo: $(pwd)\" \\\n     \"Repro command: \u003Cpaste exact mvn command from CI>\" \\\n     \"Observed failure: \u003Cpaste key Maven error lines>\" \\\n     \"Root cause guess: \u003Ccode vs build config?>\" \\\n     \"Plan: \u003Cfiles to change + why>\" \\\n     > \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt\n   ```\n   Verify it exists and is non-empty:\n   ```bash\n   test -s \u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt && echo \"notes ok\"\n   ```\n\n7. **Maven Invoker \u002F nested test projects: fix dependency resolution in the template sources, not `target\u002F**`.**\n   - If the failure is in a nested build (Invoker often runs under `target\u002Fit\u002F**` or `target\u002F**`), map the failing nested directory back to its **source template** (commonly `src\u002Fit\u002F**`, sometimes `src\u002Ftest\u002Fresources\u002F**`) and edit that template’s `pom.xml` \u002F `invoker.properties`, not generated copies under `target\u002F**`.\n   - Choose the correct modification scope by checking the nested project’s `\u003Cparent>` chain:\n     - If the nested project **does not inherit** from your reactor\u002Fparent POM, fixes must be made **inside the nested template** (or a parent POM within that template), because it won’t see your reactor `dependencyManagement\u002FpluginManagement`.\n     - If it **does inherit** from a repository parent POM, fix the parent so the nested project picks up the change naturally.\n   - Distinguish **plugin resolution** failures vs normal dependency failures; nested builds may need their own plugin versions\u002Frepositories when they don’t inherit yours.\n\n8. **Create the required patch diff file(s), then apply them to the repo.**\n   - Generate a unified diff from local edits (run in the repo root so the patch lands at `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\u002Fpatch_1.diff`):\n     ```bash\n     git diff > patch_1.diff\n     ```\n     ```bash\n     test -s patch_1.diff && echo \"patch ok\"\n     ```\n   - Prove\u002Fapply the patch artifact (separates “patch creation” from “patch application”):\n     ```bash\n     git checkout -- .\n     ```\n     ```bash\n     git apply patch_1.diff\n     ```\n   - Verify the working tree reflects the patch:\n     ```bash\n     git status\n     ```\n     ```bash\n     git diff --stat\n     ```\n\n9. **Re-run the exact CI verification command until it succeeds**, remembering `mvn verify` may run integration\u002FInvoker steps that `mvn test` does not.\n\n## Expected Result\n- You are working inside the concrete checkout directory (contains `pom.xml` and typically `.git`).\n- `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt` exists and is non-empty.\n- `patch_1.diff` exists in the repo root and is non-empty.\n- The Maven CI command (including nested\u002FInvoker builds when present) passes under the CI-declared JDK.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fmmg2skill-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-3\u002Fskills\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\u002Fmmg2skill-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-3\u002Fskills\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",[],[]]