From oracle-to-postgres-migration-expert
Generates integration testing plan for .NET data access artifacts (repos, DAOs, services) in Oracle-to-PostgreSQL migrations. Prioritizes Oracle-specific risks; outputs Markdown plan.
npx claudepluginhub passelin/marketplace-test --plugin oracle-to-postgres-migration-expertThis skill uses the workspace's default tool permissions.
Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan.
Progress:
- [ ] Step 1: Identify data access artifacts
- [ ] Step 2: Classify testing priorities
- [ ] Step 3: Write the testing plan
Step 1: Identify data access artifacts
Scope to the target project only. Find classes and methods that interact directly with the database — repositories, DAOs, stored procedure callers, service layers performing CRUD operations.
Step 2: Classify testing priorities
Rank artifacts by migration risk. Prioritize methods that use Oracle-specific features (refcursors, TO_CHAR, implicit type coercion, NO_DATA_FOUND) over simple CRUD.
Step 3: Write the testing plan
Write a markdown plan covering:
Write the plan to: .github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md
MyApp.Postgres), so each instance targets one database.