npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@adobe-thillai/aio-cli-plugin-ccua

v1.2.1

Published

Claude Code commands, agents, and skills for Adobe Commerce / Magento 2 version-upgrade work — hop planning, UCT scanning, chunked remediation, and deploy prep.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

trajendrantrajendran

Keywords

claude-codeclaudeanthropicadobe-commercemagentomagento2commerce-upgradeuctai-tools

Readme

Adobe Commerce Upgrade Toolkit

An AI-powered upgrade specialist for Adobe Commerce / Magento 2, built on Claude Code. It plans multi-hop version upgrades, runs and interprets the Upgrade Compatibility Tool (UCT), classifies and sequences breaking-change remediation, and gates deploy-readiness — so a version bump reads like a checklist instead of a research project.

Installing it drops a set of Claude Code commands, specialist agents, and skills into your Commerce project, and wires up two MCP servers the agent relies on:

  • CodeGraph — a local knowledge graph of your codebase, so the agent can jump straight to the relevant symbols and call paths for each UCT finding instead of grepping around.
  • FluffyJaws — Adobe's internal search across release notes, breaking-change docs, and support history, used for every "what changed between X and Y" lookup.

Extracted from commerce-compass as a standalone tool, so upgrade workflows can be installed, versioned, and developed independently of general Commerce module-development tooling.

Prerequisites

node >= 18
  • Claude Code CLI (claude)
  • An existing Adobe Commerce / Magento 2 project (with composer.json)

Setup

Install into your Commerce project

aio plugins:install @adobe-thillai/aio-cli-plugin-ccua
cd /path/to/commerce/project
aio ccua:setup

This copies .claude/commands, .claude/agents, .claude/skills, .claude/guardrails, .claude/prompts, .claude/context, CLAUDE.md, .mcp.json, and docs/upgrade-workflow.md into the target project, then installs and wires up the CodeGraph and FluffyJaws MCP servers.

Keep the toolkit current with:

aio ccua:update

Usage

cd /path/to/commerce/project
claude

Then:

  1. /upgrade-hop — detect current/target Commerce versions, generate a multi-hop roadmap.
  2. /upgrade-hop <version> — run the UCT scan for a hop and categorise findings.
  3. /upgrade-hop-execute <version> — implement fixes for that hop, chunk by chunk, with DI-compile/PHPCS/PHPUnit validation after each.
  4. /upgrade-deploy-prep — deploy-readiness gate once all hops are complete.

See docs/upgrade-workflow.md for the full workflow diagram and CLAUDE.md for the complete behavior contract (scope, skills reference, quality gates).

What's included

  • Commands: upgrade-hop, upgrade-hop-execute, upgrade-deploy-prep
  • Agents: commerce-upgrade-analyst (primary driver) plus supporting specialists (commerce-architect, commerce-devops-engineer, commerce-qa-engineer, commerce-frontend-developer, commerce-security-reviewer)
  • Skills: UCT scanning, breaking-change analysis, remediation ordering, marketplace extension compatibility, data migration planning, encryption/password rotation, ECE-tools config, PCI checklist, environment detection, and more — see CLAUDE.md §13.

Known gaps

  • upgrade-hop.md / upgrade-hop-execute.md reference a no-git-operations skill that was never authored in the source repo this was extracted from. Until it exists, the constraint (no git operations from dispatched sub-agents during a hop) is applied literally per CLAUDE.md.