npx skills add https://github.com/obra/superpowers --skill test-driven-developmentHow Planning Oracle To Postgres Migration Integration Testing fits into a Paperclip company.
Planning Oracle To Postgres Migration Integration Testing drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.
Pre-configured AI company — 18 agents, 18 skills, one-time purchase.
SKILL.md44 linesExpandCollapse
---name: planning-oracle-to-postgres-migration-integration-testingdescription: 'Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.'--- # Planning Integration Testing for Oracle-to-PostgreSQL Migration Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan. ## Workflow ```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:- List of testable artifacts with method signatures- Recommended test cases per artifact- Seed data requirements- Known Oracle→PostgreSQL behavioral differences to validate ## Output Write the plan to: `.github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md` ## Key Constraints - **Single project scope** — only plan tests for artifacts within the target project.- **Database interactions only** — skip business logic that does not touch the database.- **Oracle is the golden source** — tests should capture Oracle's expected behavior for comparison against PostgreSQL.- **No multi-connection harnessing** — migrated applications are copied and renamed (e.g., `MyApp.Postgres`), so each instance targets one database.Add Educational Comments
Takes any code file and transforms it into a teaching resource by adding educational comments that explain syntax, design choices, and language concepts. Automa
Agent Governance
When your AI agents start calling APIs, touching databases, or executing shell commands, you need guardrails before something goes sideways. This gives you comp
Agentic Eval
Implements self-critique loops where Claude generates output, evaluates it against your criteria, then refines based on its own feedback. Includes evaluator-opt