[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BKVF3T079XVTJACACK75VJ":3,"skill-same:01M7BKVF3T079XVTJACACK75VJ":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},"01M7BKVF3T079XVTJACACK75VJ","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\u002Fskillhone-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-1\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# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Core rule: reproduce the target CI before changing the project\n\nFor build-repair tasks, the first successful local command is not enough. The\nfailure must be reproduced under the toolchain and Maven command used by the\ntarget CI. Read the repository's CI configuration (`.travis.yml`, workflow\nfiles, wrapper scripts, build POMs) before interpreting any compiler or\ndependency error.\n\nRecord at least:\n\n```bash\njava -version\njavac -version\nmvn -version\n```\n\nIf the repository declares a historical JDK and the container's default Java\nis newer, switch to the declared JDK *before* patching project files. A failure\ncaused only by running an old project on a modern JDK is not evidence that the\nproject should be migrated.\n\nFor environments that provide the BugSwarm JDK switcher, a JDK 7 Travis build\ncan be reproduced with:\n\n```bash\nsource \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\njdk_switcher use openjdk7\nexport TRAVIS_JDK_VERSION=openjdk7\njava -version\n```\n\nThen run the exact CI build command, including any non-default reactor POM and\nflags:\n\n```bash\n# Example only — replace `-f ...` and flags with the repository's CI command.\nmvn -Dhttps.protocols=TLSv1.2 -B -U -f \u003Creactor-pom.xml> verify --fail-at-end\n```\n\n## Maven Invoker integration tests (nested projects)\n\nSome Maven builds run integration tests via `maven-invoker-plugin` (often during\n`verify`). These tests execute Maven in *nested sample projects* (commonly under\n`src\u002Fit\u002F**`), which changes how you should interpret dependency failures.\n\nKey implications:\n\n- **Dependency resolution is scoped to the nested project.** `dependencyManagement`,\n  `pluginManagement`, and `\u003Crepositories>` from the main build do not apply unless\n  the nested project's `pom.xml` explicitly inherits them.\n- **Invoker runs may use an isolated local repository** under `target\u002F**`. A missing\n  artifact can mean it was never installed into the invoker repo, not that the\n  main reactor failed to build it.\n\nWhen a nested project fails to resolve an artifact\u002Fplugin:\n\n1. Identify which invoker project failed (from CI logs or `target\u002Finvoker-reports\u002F`).\n2. Inspect the **source-controlled template** under `src\u002Fit\u002F...` and any invoker\n   `settings.xml` \u002F `invoker.properties` used for those runs.\n3. Check the invoker configuration in the real build POM for how it seeds the local\n   repo (e.g. `invoker:install`, `installArtifacts`, setup goals) and which settings\n   file\u002Frepositories it uses.\n\nTo iterate faster, many invoker setups support running a single project and\nstreaming logs, for example:\n\n```bash\nmvn -pl \u003Cmodule-running-invoker> -Dinvoker.test=\u003Cproject-pattern> -Dinvoker.streamLogs=true verify\n```\n\nModification scope rule for invoker tests:\n\n- **Never edit `target\u002F**`** (cloned test projects, invoker local repositories, or\n  generated reports). Those directories are regenerated; fixes must be made in the\n  real module POM(s) and\u002For under `src\u002Fit\u002F**` templates so they are captured in\n  patches and version control.\n\n### Do not modernize away historical-JDK symptoms\n\nWhen CI declares JDK 7, do **not** respond to a default-JDK-11 failure by\nblindly doing any of the following:\n\n- changing Java source\u002Ftarget solely to make the project compile on Java 11;\n- removing or excluding `com.sun:tools` \u002F `tools.jar` solely because Java 9+\n  no longer ships it;\n- adding replacement annotation APIs solely for `javax.annotation.Generated`;\n- changing production logic because javac's post-Java-8 module model produces\n  different compiler-element behavior.\n\nFirst reproduce on the declared JDK. Only errors that remain under the target\nCI environment should drive the repair.\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nBefore finishing:\n\n1. Write your diagnosis and plan to the task-specified notes file (commonly\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`).\n2. Create at least one non-empty standard unified diff at the task-specified patch\n   path (commonly `\u003Crepo_path>\u002Fpatch_1.diff`) containing the intended\n   source\u002Fconfiguration change.\n3. Apply that patch to the failed repository.\n4. Check `git diff`\u002F`git status` and ensure the intended project file—not only the\n   patch artifact—was changed.\n5. Re-run the exact CI verification command under the CI-declared toolchain\u002FJDK.\n6. Do not finish until the full reactor, including Maven Invoker integration tests,\n   succeeds.\n\n## Minimal diagnostic sequence\n\n```bash\nREPO=\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\ncd \"$REPO\"\n\n# 1. Establish target CI and toolchain.\nsed -n '1,220p' .travis.yml\njava -version\njavac -version\nmvn -version\n\n# If CI declares a specific JDK and a switcher is available, switch first.\nif [ -f \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh ]; then\n  source \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\n  jdk_switcher use \u003Cci-jdk>   # e.g., openjdk7\n  export TRAVIS_JDK_VERSION=\u003Cci-jdk>\nfi\njava -version\n\n# 2. Reproduce the real CI command (replace with the actual command\u002Fflags).\nmvn -B -U -f \u003Creactor-pom.xml> verify --fail-at-end\n\n```\n\n## General Maven lifecycle reminders\n\n- `mvn test` does not imply that `mvn verify` passes. `verify` can execute\n  integration-test and Invoker steps that `test` never reaches.\n- A green command run under the wrong JDK is not sufficient evidence of a\n  valid CI repair.\n","# Maven Build Lifecycle — Legacy CI Repair Workflow\n\n## Core rule: reproduce the target CI before changing the project\n\nFor build-repair tasks, the first successful local command is not enough. The\nfailure must be reproduced under the toolchain and Maven command used by the\ntarget CI. Read the repository's CI configuration (`.travis.yml`, workflow\nfiles, wrapper scripts, build POMs) before interpreting any compiler or\ndependency error.\n\nRecord at least:\n\n```bash\njava -version\njavac -version\nmvn -version\n```\n\nIf the repository declares a historical JDK and the container's default Java\nis newer, switch to the declared JDK *before* patching project files. A failure\ncaused only by running an old project on a modern JDK is not evidence that the\nproject should be migrated.\n\nFor environments that provide the BugSwarm JDK switcher, a JDK 7 Travis build\ncan be reproduced with:\n\n```bash\nsource \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\njdk_switcher use openjdk7\nexport TRAVIS_JDK_VERSION=openjdk7\njava -version\n```\n\nThen run the exact CI build command, including any non-default reactor POM and\nflags:\n\n```bash\n# Example only — replace `-f ...` and flags with the repository's CI command.\nmvn -Dhttps.protocols=TLSv1.2 -B -U -f \u003Creactor-pom.xml> verify --fail-at-end\n```\n\n## Maven Invoker integration tests (nested projects)\n\nSome Maven builds run integration tests via `maven-invoker-plugin` (often during\n`verify`). These tests execute Maven in *nested sample projects* (commonly under\n`src\u002Fit\u002F**`), which changes how you should interpret dependency failures.\n\nKey implications:\n\n- **Dependency resolution is scoped to the nested project.** `dependencyManagement`,\n  `pluginManagement`, and `\u003Crepositories>` from the main build do not apply unless\n  the nested project's `pom.xml` explicitly inherits them.\n- **Invoker runs may use an isolated local repository** under `target\u002F**`. A missing\n  artifact can mean it was never installed into the invoker repo, not that the\n  main reactor failed to build it.\n\nWhen a nested project fails to resolve an artifact\u002Fplugin:\n\n1. Identify which invoker project failed (from CI logs or `target\u002Finvoker-reports\u002F`).\n2. Inspect the **source-controlled template** under `src\u002Fit\u002F...` and any invoker\n   `settings.xml` \u002F `invoker.properties` used for those runs.\n3. Check the invoker configuration in the real build POM for how it seeds the local\n   repo (e.g. `invoker:install`, `installArtifacts`, setup goals) and which settings\n   file\u002Frepositories it uses.\n\nTo iterate faster, many invoker setups support running a single project and\nstreaming logs, for example:\n\n```bash\nmvn -pl \u003Cmodule-running-invoker> -Dinvoker.test=\u003Cproject-pattern> -Dinvoker.streamLogs=true verify\n```\n\nModification scope rule for invoker tests:\n\n- **Never edit `target\u002F**`** (cloned test projects, invoker local repositories, or\n  generated reports). Those directories are regenerated; fixes must be made in the\n  real module POM(s) and\u002For under `src\u002Fit\u002F**` templates so they are captured in\n  patches and version control.\n\n### Do not modernize away historical-JDK symptoms\n\nWhen CI declares JDK 7, do **not** respond to a default-JDK-11 failure by\nblindly doing any of the following:\n\n- changing Java source\u002Ftarget solely to make the project compile on Java 11;\n- removing or excluding `com.sun:tools` \u002F `tools.jar` solely because Java 9+\n  no longer ships it;\n- adding replacement annotation APIs solely for `javax.annotation.Generated`;\n- changing production logic because javac's post-Java-8 module model produces\n  different compiler-element behavior.\n\nFirst reproduce on the declared JDK. Only errors that remain under the target\nCI environment should drive the repair.\n\n## Build-repair artifact contract\n\nThis benchmark requires both a diagnosis artifact and an applicable patch.\nBefore finishing:\n\n1. Write your diagnosis and plan to the task-specified notes file (commonly\n   `\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002Ffailed_reasons.txt`).\n2. Create at least one non-empty standard unified diff at the task-specified patch\n   path (commonly `\u003Crepo_path>\u002Fpatch_1.diff`) containing the intended\n   source\u002Fconfiguration change.\n3. Apply that patch to the failed repository.\n4. Check `git diff`\u002F`git status` and ensure the intended project file—not only the\n   patch artifact—was changed.\n5. Re-run the exact CI verification command under the CI-declared toolchain\u002FJDK.\n6. Do not finish until the full reactor, including Maven Invoker integration tests,\n   succeeds.\n\n## Minimal diagnostic sequence\n\n```bash\nREPO=\u002Fhome\u002Ftravis\u002Fbuild\u002Ffailed\u002F\u003Crepo>\u002F\u003Cid>\ncd \"$REPO\"\n\n# 1. Establish target CI and toolchain.\nsed -n '1,220p' .travis.yml\njava -version\njavac -version\nmvn -version\n\n# If CI declares a specific JDK and a switcher is available, switch first.\nif [ -f \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh ]; then\n  source \u002Fopt\u002Fjdk_switcher\u002Fjdk_switcher.sh\n  jdk_switcher use \u003Cci-jdk>   # e.g., openjdk7\n  export TRAVIS_JDK_VERSION=\u003Cci-jdk>\nfi\njava -version\n\n# 2. Reproduce the real CI command (replace with the actual command\u002Fflags).\nmvn -B -U -f \u003Creactor-pom.xml> verify --fail-at-end\n\n```\n\n## General Maven lifecycle reminders\n\n- `mvn test` does not imply that `mvn verify` passes. `verify` can execute\n  integration-test and Invoker steps that `test` never reaches.\n- A green command run under the wrong JDK is not sufficient evidence of a\n  valid CI repair.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","controlled-skill-repair-experiments\u002Fresult\u002Fskillhone-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-1\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\u002Fskillhone-gpt5.2-xhigh\u002Fcandidates\u002Fsingle-fix-build-google-auto-RI-002\u002Fround-1\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",[],[]]