- Home
- Skills
- Agents & Orchestration
- sandbox cleanup development
sandbox cleanup development
Build and integrate Java AST transformations, multi-file cleanups, and JDT quick fixes for the Sandbox repository.
$20
Works with the AI Agents you already use
sandbox cleanup development
Example session with this skill installed
I need to create a multi-file cleanup that renames a specific internal annotation and updates all its call sites across the project. How should I structure this in Sandbox?
- Read your context and instructions
- Compiled the sandbox cleanup development
I have designed the structure for a coordinated multi-file cleanup to rename the annotation and update all call sites. This implementation uses the AbstractPlannedMultiFileCleanUp path to ensure semantic consistency across compilation units.
Coordinated Cleanup Design
| Component | Implementation Detail |
|---|---|
| Target | carstenartur/sandbox (Current Revision) |
| Approach | AbstractPlannedMultiFileCleanUp<AnnotationRenamePlan> |
| Discovery | Search for ITypeBinding of the target annotation within project scope |
| Planning | Map all ICompilationUnit occurrences to a single AnnotationRenamePlan |
| Rewrite | Use ASTRewrite to modify AnnotationTypeDeclaration and Annotation nodes |
| Safety | Reject if annotation is part of a binary dependency or read-only file |
public class RenameInternalAnnotationCleanUp extends AbstractPlannedMultiFileCleanUp<AnnotationRenamePlan> {
@Override
protected AnnotationRenamePlan createPlan(ICompilationUnit[] units) {
// Discovery phase: Identify annotation and all reference sites
return new AnnotationRenamePlan(units);
}
@Override
protected ICleanUpFix createFix(ICompilationUnit unit, AnnotationRenamePlan plan) {
// Per-file rewrite phase: Apply the name change to the AST
return new AnnotationRenameFix(unit, plan);
}
}
Next steps
- Register the new cleanup class in
MYCleanUpConstantsand the corresponding extension point. - Add a test case to the existing JUnit suite using a mock project with two dependent source files.
- Verify that the UI wizard correctly shows a preview of changes in both the declaration and usage files.
Connects securely to your tools. The creator never sees your data.
About this skill
Developing Java AST transformations within the Eclipse JDT ecosystem is fragile. Manual implementations often break source compatibility, lose comments, or fail to handle complex multi-file dependencies. This skill provides a structured framework for building cleanups, quick fixes, and TriggerPattern rules specifically for the carstenartur/sandbox repository and its host environment.
What it does
- AST transformations designs Java cleanup rules using fluent visitors and JDT rewrite infrastructure.
- Multi-file coordination manages semantically coupled edits across different compilation units using a planned lifecycle.
- Pattern matching implements TriggerPattern rules with specific DSL guards and applicability contracts.
- Upstream assessment evaluates the effort required to port Sandbox implementations to standard Eclipse JDT.
- Integration testing extends existing Maven and JUnit fixtures to verify UI behavior, headless execution, and save actions.
How it works
- Define the contract by identifying the entry point, target Java level, and whether the change is local or multi-file.
- Select the API from TriggerPattern, Sandbox fluent visitors, or raw JDT rewrite based on the complexity of analysis required.
- Plan the edits using
AbstractPlannedMultiFileCleanUpto separate discovery, planning, and per-file rewrites. - Execute verification by running repository-specific gates to test stale sources, partial selections, and undo/redo behavior.
Frameworks & tools
This skill works with Java, Eclipse JDT (Java Development Tools), LTK (Language Toolkit), Maven, and the Sandbox repository infrastructure.
Why this beats prompting it yourself
Writing JDT cleanups requires strict adherence to binding resolutions and AST lifecycles that generic models often hallucinate. This skill enforces the specific multi-file contracts and registration patterns required by the Sandbox repository, preventing broken project structures.
Use cases
- Add a new code cleanup rule to remove redundant logic across a workspace.
- Implement a quick fix that coordinates changes between a class and its interface.
- Port a custom Sandbox transformation to an upstream Eclipse JDT plugin.
- Create a TriggerPattern to enforce team-specific coding standards.
Known limitations
This is an authoring skill only. It requires an existing checkout of the Sandbox repository and does not include a live Eclipse instance or compiler.
Requires a local checkout of the Sandbox repository. Does not provide an Eclipse execution environment or compiler. Coordination limited to supported host capabilities.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 14 days ago
Requires
Permissions
Allowed Hosts