Delete .srcx/ directories from project root and included builds.
npx skills add https://github.com/ClankerGuru/opsx --skill srcx-clean
Please help me install this Agent Skill. Skill: srcx-clean Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/srcx-clean Command: npx skills add https://github.com/ClankerGuru/opsx --skill srcx-clean
Remove the .srcx/ directories in the workspace to reset srcx context reports, ensuring fresh context before regeneration.
Execute the Gradle task to clean the srcx context using ./gradlew -q srcx-clean
High-intent search queries and answers about installing and using this skill.
Run the ./gradlew -q srcx-clean task to delete .srcx/ directories at the project root and in included builds, clearing stale artifacts before regenerating fresh context data.
The best way to reset stale srcx context reports is running the srcx-clean Gradle task to wipe the .srcx/ directories, ensuring fresh context before regeneration and avoiding contamination from previous runs.
Yes, you need the zone.clanker.srcx plugin applied to clean the .srcx workspace context. You must also ensure no tooling currently relies on the context being present before deleting the directories.
You should wipe the srcx output before full rewrites or audits of AI-generated workspace tasks to avoid contamination from previous runs, ensuring reliable regeneration of context reports by clearing stale artifacts.
The ./gradlew -q srcx-clean command deletes the .srcx/ directories located in the project root and in each included build, resetting the srcx context reports across your entire Gradle workspace.
ClankerGuruRegenerate .srcx/ codebase context reports from Kotlin source via Gradle.
sobhanashineClear existing freeze boundaries across all directories in a workspace.
ClankerGuruWire Gradle composite builds with includeBuild and dependency substitution across repositories.
richfremRemove stale agent lock directories under context/.locks/ using Python 3.8+.
