anthropics/commerce-agents Reference blueprint for building shopping and merchant agents with Claude. Examples in retail, commerce, telecom, and entertainment included. |
for people* (7/10)
for AI* (7/9)
Rule-of-thumb estimates
Rebuild value
Maintenance effort
analysis.maintainabilityScores.- Unit size6.8−0.616% of unit code in units > 50 lines
For people: Long functions do many things at once: they are hard to name, read, test and reuse.
For AI agents: To change one line, an agent reads and often rewrites the whole function: bigger edits, more tokens, more breakage.
- Duplication5.8−0.511% of main code duplicated
For people: A fix in one copy must be repeated in all the others; a missed copy becomes a bug.
For AI agents: Agents copy the patterns they find, so duplicates multiply; a change to one copy misses the others, and every copy costs context.
- Unit complexity8.3−0.44% of unit code with McCabe > 25
For people: Every branch is another path to understand and test; complex logic is where mistakes are made and missed in review.
For AI agents: Nested conditions are where generated changes break edge cases; complex units need more tests and review before an agent's change can be trusted.
- File size5.5−0.426% of main code in files > 500 lines
For people: Large files are hard to navigate, mix responsibilities and attract merge conflicts.
For AI agents: Agents read whole files into their context: every change to a large file costs many tokens and crowds out other relevant code.
- Volume8.9−0.112,060 lines of main code
For people: More code is more to learn, search and keep in mind; onboarding and judging a change's impact slow down as it grows.
For AI agents: An agent sees only a slice at a time: the bigger the code base, the more it searches, and the likelier it misses relevant code or rewrites an existing helper.
- File complexity8.8−0.16% of main code in files with McCabe sum > 125
For people: Complex files concentrate risk: understanding one means keeping many paths in mind.
For AI agents: Much to read and much logic to get right in one place: the costliest combination for an agent.
- Test code8.6−0.162 test lines per 100 main lines
For people: Tests document the intended behaviour and make changes safe.
For AI agents: Tests let an agent check its own work; without them its mistakes surface later, in review or in production.
- File size5.5−0.926% of main code in files > 500 lines
For AI agents: Agents read whole files into their context: every change to a large file costs many tokens and crowds out other relevant code.
For people: Large files are hard to navigate, mix responsibilities and attract merge conflicts.
- Duplication5.8−0.711% of main code duplicated
For AI agents: Agents copy the patterns they find, so duplicates multiply; a change to one copy misses the others, and every copy costs context.
For people: A fix in one copy must be repeated in all the others; a missed copy becomes a bug.
- Unit size6.8−0.316% of unit code in units > 50 lines
For AI agents: To change one line, an agent reads and often rewrites the whole function: bigger edits, more tokens, more breakage.
For people: Long functions do many things at once: they are hard to name, read, test and reuse.
- Unit complexity8.3−0.24% of unit code with McCabe > 25
For AI agents: Nested conditions are where generated changes break edge cases; complex units need more tests and review before an agent's change can be trusted.
For people: Every branch is another path to understand and test; complex logic is where mistakes are made and missed in review.
- Test code8.6−0.262 test lines per 100 main lines
For AI agents: Tests let an agent check its own work; without them its mistakes surface later, in review or in production.
For people: Tests document the intended behaviour and make changes safe.
- Volume8.9−0.112,060 lines of main code
For AI agents: An agent sees only a slice at a time: the bigger the code base, the more it searches, and the likelier it misses relevant code or rewrites an existing helper.
For people: More code is more to learn, search and keep in mind; onboarding and judging a change's impact slow down as it grows.
- File complexity8.8−0.16% of main code in files with McCabe sum > 125
For AI agents: Much to read and much logic to get right in one place: the costliest combination for an agent.
For people: Complex files concentrate risk: understanding one means keeping many paths in mind.
- 1check.pyscripts/McCabe 207647 LOC
- 2turn.pycommerce-common/commerce_common/McCabe 109419 LOC
- 3run_demo.pyscripts/McCabe 85286 LOC
- 4enrichment.pymerchant-agent/core/merchant_agent/McCabe 83367 LOC
- 5memory.pycommerce-common/commerce_common/McCabe 55451 LOC
- 6enrichment.pyshopping-agent/core/shopping_agent/McCabe 53248 LOC
- 7agent_sdk.pycommerce-common/commerce_common/McCabe 48199 LOC
- 8serialization.pyshopping-agent/core/shopping_agent/McCabe 45104 LOC
- 9streaming.pycommerce-common/commerce_common/McCabe 41173 LOC
- 10manifest.pycommerce-common/commerce_common/McCabe 38143 LOC
| Standard analyses: | Main Code: 12,060 LOC (75 files) = PY (95%) + YAML (3%) + TOML (<1%) Secondary code: Test: 7,464 LOC (49); Generated: 1,881 LOC (1); Build & Deploy: 357 LOC (13); Other: 53,013 LOC (420); |
||
| Duplication: 10% | |||
| File Size: 0% long (>1000 LOC), 36% short (<= 200 LOC) | |||
|
|
Logical Component Decomposition: primary (5 components) | ||
| Goals: Keep the system simple and easy to change (4) | |||
| Experimental analyses (less reliable heuristic analyses): | |||
| Unit Size: 6% long (>100 LOC), 62% short (<= 10 LOC) | |||
| Conditional Complexity: 4% complex (McCabe index > 50), 54% simple (McCabe index <= 5) | |||
|
|
Static Component Dependencies: primary (5 components) | ||
No commit history found.
Visual Code Explorers
| MAIN (75) | Circles | Sunburst | |
| TEST (49) | Circles | Sunburst | |
| BUILD AND DEPLOYMENT (13) | Circles | Sunburst | |
| GENERATED (1) | Circles | Sunburst | |
| OTHER (420) | Circles | Sunburst |
File Visualizations
File size views:
Duplication views:
File age views:
File change frequency views:
Contributors per file views:
Contributor Visualizations
Contributor dependency views:
Components and Dependencies Visualizations
| Components | Temporal Dependencies | Duplication | Commits Racing Charts | ||||||||||
| 30 days | 3 months | 6 months | |||||||||||
| PRIMARY (5) | Bubble Chart | Tree Map |
2D
|
3D
|
2D
|
3D
|
2D
|
3D
|
All Time | 12 Months | |||
File Dependencies Visualizations
Temporal dependencies among files:
|
Units Visualizations
Unit size and conditional complexity views:
Lists of Files Per Scope
- MAIN (75 files)
- TEST (49 files)
- BUILD AND DEPLOYMENT (13 files)
- GENERATED (1 file)
- OTHER (420 files)
- FILES: History Data
- IGNORED FILES: By Extension | By Rule
Analysis Results
- CONFIGURATION: JSON
- ALL ANALYSIS RESULTS: JSON
- DUPLICATES: TXT | JSON
- UNITS: TXT | JSON
- CONTRIBUTORS: TXT | JSON
- LOGICAL DECOMPOSITIONS: JSON
- CONCERNS: JSON
- CONTROLS: TXT
- ALL METRICS: TXT