skills.rest
Pear-Commerce
Pear-CommerceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

upc-resolution-code-changes

Validate UPC resolution code changes with unit tests and devdb verification.

Updated May 15, 2026
Search Tags:#unit testing#api development#regression prevention#code verification#retailer integration#upc resolution#devdb testing
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill upc-resolution-code-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upc-resolution-code-changes
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/upc-resolution-code-changes
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill upc-resolution-code-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Modifying the UPC resolution system that matches products to their correct UPCs across multiple retailers carries high risk of breaking existing functionality, causing incorrect product matches, or introducing regressions that only appear with live retailer data. This skill provides a structured guardrail to ensure all changes follow Pear's engineering standards, include proper test coverage, and are verified against a live dev database before merging.

Core Features & Use Cases

  • Structured Code Change Guardrails: Enforces Pear's workflow for modifications to the UPC resolution graph, resolver logic, TinEye image comparison, direct/trusted candidate scoring, retailer UPC feasibility scripts, and known item detail resolution in api.pearcommerce.com.
  • Focused Test Requirements: Mandates adding targeted deterministic unit tests for exact touched behavior, including standard test classes for UPC resolution components, graph logic, and retailer resolvers.
  • Local Devdb Verification: Provides a known-good sample of live retailer tests, environment configuration, and workflow steps to catch regressions from live data drift, including handling for known master-failing tests. Use case: For example, if you are updating the UPC resolver to add support for a new grocery retailer with sparse UPC data, this skill ensures you follow required code patterns, add tests for the new resolver, run focused unit checks, and verify the change works with live retailer data via the devdb sample before marking work complete.

Quick Start

Use the upc-resolution-code-changes skill when modifying any UPC resolution logic in api.pearcommerce.com to follow the required code change workflow, run focused unit tests, and complete local devdb verification before marking the work done.

Frequently Asked Questions about upc-resolution-code-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify UPC resolution code changes without breaking existing retailer product matches?▼

To verify UPC resolution code changes safely, add focused deterministic unit tests for the touched behavior and run local devdb verification against known-good retailer test samples to prevent regressions in cross-retailer product matching.

What is the best way to test modifications to a UPC resolver and graph search logic?▼

The best way to test UPC resolver and graph search logic modifications is by adding targeted deterministic unit tests for the exact touched behavior, supplemented by local devdb verification to catch regressions caused by live retailer data drift.

Do I need a development database to test cross-retailer UPC feasibility scripts?▼

Yes, you need a local devdb to test cross-retailer UPC feasibility scripts. Local devdb verification using provided environment configuration and known-good live retailer test samples is required to catch cross-retailer product matching regressions before merging.

How does local devdb verification prevent regressions in API product matching behavior?▼

Local devdb verification prevents regressions by testing code changes against a known-good sample of live retailer tests and environment configuration. This process catches issues from live data drift and known master-failing tests before merging.

What testing is required when updating TinEye image comparison logic for UPC resolution?▼

When updating TinEye image comparison logic for UPC resolution, you must add focused deterministic unit tests for the exact touched behavior and complete local devdb verification using known-good test samples to ensure existing cross-retailer matching behavior remains intact.

Why does updating direct and trusted candidate scoring require devdb verification?▼

Updating direct and trusted candidate scoring requires devdb verification because live retailer data drift can introduce hidden regressions. Verifying against a known-good sample of live retailer tests ensures scoring changes do not break existing cross-retailer product matching behavior.

Related Skills

Explore More Software Engineering Skills→
Pear-CommercePear-Commerce

retailer-upc-resolution-feasibility

Validate retailer UPC-to-item-ID and PDP URL resolution via proxy-backed Java probes.

Official
Advanced
hoklimshoklims

oco-verify-fix

Run build, type, lint, and test commands to validate code changes.

Community
Advanced
forcedotcomforcedotcom
803

running-apex-tests

Execute Salesforce Apex unit tests with coverage analysis and failure diagnosis.

Official
Advanced
seankao31seankao31

mutation-testing

Apply mutation testing to evaluate test suite quality and reveal defects.

Community
Advanced