AGENTS.md · git:20260930.bb552fb · 2026-09-30 · sha256 91e18a31f470ba17
AGENTS.md git:20260930.bb552fbA
Immutable. This exact content never changes and is served at /api/v1/blob/91e18a31f470ba17.
<!-- SPDX-License-Identifier: CC-BY-SA-4.0 -->
<!-- SPDX-FileCopyrightText: Netresearch DTT GmbH -->
# TYPO3 Extension Upgrade Skill
Agent harness for the TYPO3 extension upgrade skill repository.
## Repo Structure
```
├── skills/typo3-extension-upgrade/ # Skill definition
│ ├── SKILL.md # Main skill instructions
│ ├── assets/ # Config templates (rector, fractor, phpstan, phpunit)
│ ├── checkpoints.yaml # Eval checkpoints
│ ├── references/ # Detailed upgrade docs per version
│ └── scripts/ # scan-deprecations.sh (report-only grep scan)
├── agents/ # Agent definitions
│ └── upgrade-planner.md # Upgrade planning agent
├── commands/ # Slash commands
│ ├── assess.md # /assess command
│ └── rector.md # /rector command
├── evals/ # Evaluation suite
│ ├── evals.json
│ └── run-ab-test.sh # A/B run via the claude CLI (paid, manual only)
├── Build/ # Build tooling
│ ├── Scripts/ # Utility scripts
│ └── hooks/ # Git hooks (pre-push)
├── composer.json # Composer package (ai-agent-skill type)
├── docs/ # Architecture and planning docs
│ └── ARCHITECTURE.md
├── scripts/ # Harness scripts
│ └── verify-harness.sh
└── tests/ # Behaviour tests for the shell scripts
└── test_scripts.py
```
## Commands
No build system scripts defined in `composer.json`. Repository commands:
- `python3 tests/test_scripts.py` -- behaviour tests for the shell scripts (CI: `.github/workflows/tests.yml`)
- `bash scripts/verify-harness.sh` -- local agent harness check
Key skill commands (run in target extension, not this repo):
- `./vendor/bin/rector process --dry-run` -- Rector PHP migrations
- `./vendor/bin/fractor process --dry-run` -- Fractor non-PHP migrations
- `./vendor/bin/phpstan analyse` -- Static analysis
- `./vendor/bin/php-cs-fixer fix` -- Code style fixes
## Rules
- **Scope**: Extension code upgrades only; NOT for TYPO3 project/core upgrades
- **Workflow**: Always complete planning phase before code changes (see `references/pre-upgrade.md`)
- **Caution**: Do NOT blindly apply Rector/Fractor for dual-version compatibility or untested extensions
- **Verification**: Always verify success criteria after upgrade (see `references/verification.md`)
- **Assets**: Config templates in `assets/` are starting points; adapt per extension
## References
- [SKILL.md](skills/typo3-extension-upgrade/SKILL.md) -- Main skill definition
- [Pre-upgrade checklist](skills/typo3-extension-upgrade/references/pre-upgrade.md)
- [API changes by version](skills/typo3-extension-upgrade/references/api-changes.md)
- [v13 to v14 upgrade guide](skills/typo3-extension-upgrade/references/upgrade-v13-to-v14.md)
- [Dual compatibility guide](skills/typo3-extension-upgrade/references/dual-compatibility.md)
- [Verification criteria](skills/typo3-extension-upgrade/references/verification.md)
- [Troubleshooting](skills/typo3-extension-upgrade/references/troubleshooting.md)
- [Upgrade planner agent](agents/upgrade-planner.md)