Skip to content

Latest commit

 

History

History
69 lines (60 loc) · 4.3 KB

File metadata and controls

69 lines (60 loc) · 4.3 KB

AGENTS.md — TYPO3 Core Contributions Skill

Repo Structure

├── skills/typo3-core-contributions/
│   ├── SKILL.md                         # Main skill definition
│   ├── references/                      # Reference documentation
│   │   ├── account-setup.md
│   │   ├── commit-message-format.md
│   │   ├── commit-msg-hook.md
│   │   ├── ddev-setup-workflow.md
│   │   ├── forge-api.md
│   │   ├── gerrit-review-patterns.md
│   │   ├── gerrit-workflow.md
│   │   ├── modern-typo3-patterns.md
│   │   ├── t3o-gitlab-workflow.md
│   │   └── troubleshooting.md
│   └── scripts/                         # Automation scripts
│       ├── create-commit-message.py
│       ├── create-forge-issue.sh
│       ├── query-forge-metadata.sh
│       ├── setup-typo3-coredev.sh
│       ├── t3o-gitlab.py
│       ├── validate-commit-message.py
│       └── verify-prerequisites.sh
├── .github/workflows/                   # CI workflows
├── assets/                              # Images and diagrams
├── Build/                               # Build tooling
├── evals/                               # Skill evaluations
├── docs/                                # Architecture and plans
│   ├── ARCHITECTURE.md
│   └── exec-plans/
└── composer.json                        # Package definition

Commands

No Makefile or npm scripts. Key scripts live in skills/typo3-core-contributions/scripts/:

  • bash skills/typo3-core-contributions/scripts/verify-prerequisites.sh — check TYPO3 account, Gerrit SSH, Git config
  • bash skills/typo3-core-contributions/scripts/setup-typo3-coredev.sh — automated TYPO3 Core dev environment setup
  • python3 skills/typo3-core-contributions/scripts/validate-commit-message.py — validate commit message format
  • python3 skills/typo3-core-contributions/scripts/create-commit-message.py — generate compliant commit messages
  • python3 skills/typo3-core-contributions/scripts/t3o-gitlab.py — git.typo3.org helper: access level, issues, merge requests, links, bot-wall probe

Rules

  1. Route by host firstreview.typo3.org is Gerrit (Core), forge.typo3.org is Redmine (Core issues), git.typo3.org/services/t3o-sites/** is ordinary GitLab for the t3o sites. Only git.typo3.org/typo3/CI/cms belongs to the Core workflow
  2. Gerrit, not GitHub PRs — TYPO3 Core uses Gerrit (review.typo3.org) for code review. t3o site repositories use GitLab merge requests instead, against develop, never merged by their author
  3. Commit message format — must start with [TYPE] (BUGFIX, FEATURE, TASK, DOCS, CLEANUP, SECURITY), include Resolves: #<issue> and Releases: lines
  4. WIP workflow — submit as WIP first (refs/for/main%wip), mark ready only after CI passes
  5. Preserve Change-Id — always amend commits to keep the Gerrit Change-Id
  6. Analyze before coding — understand the issue deeply before writing any fix
  7. Fix ALL CI failures in one patchset — do not iterate one failure at a time
  8. Scope boundary — this skill covers code contributions only; documentation contributions use typo3-docs-skill
  9. Verify a write, never a status code — on git.typo3.org a label write below Reporter answers HTTP 200 and drops the field; read the returned object back
  10. Fingerprint live responses from t3o sitesextensions.typo3.org is behind Anubis, which serves an HTTP 200 text/html challenge page to browser user agents

References