skills.rest
dirnbauer
dirnbauerCOMMUNITY
Explore all skills by this author →
Website𝕏@KDirnbauerGitHub

typo3-core-contributions

Guide TYPO3 core contributions from account setup to Gerrit patch submission.

33|6|Updated Jan 2, 2026
Search Tags:#git#workflow#patch#code-review#TYPO3#Gerrit
One-click install
npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-core-contributions-dirnbauer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typo3-core-contributions
Source: https://github.com/dirnbauer/webconsulting-skills/tree/main/skills/typo3-core-contributions
Command: npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-core-contributions-dirnbauer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a complete, repeatable workflow for TYPO3 core contributions, guiding developers from account setup and Gerrit configuration to patch creation, review, and documentation.

Core Features & Use Cases

  • End-to-end contribution workflow: from forge issues to Gerrit patch submission and review.
  • Environment setup & best practices: Git config, Change-Id hooks, and branch management for TYPO3 patches.
  • Use Case: When contributing a bug fix to TYPO3 core, follow this skill to create a patch, attach it to a Gerrit review, and track the review process until acceptance.

Quick Start

Clone TYPO3 core, configure Gerrit, create a feature patch, and push for review.

Frequently Asked Questions about typo3-core-contributions

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

FAQPage Schema
How do I submit a patch to TYPO3 core using Gerrit?▼

Contributing to TYPO3 core requires setting up a TYPO3.org account, configuring Gerrit authentication keys, and installing Git hooks for Change-Id generation. You also need a local clone of the TYPO3 core repository to create and manage your patches.

Why does my TYPO3 Gerrit patch submission fail without a Change-Id?▼

TYPO3 Gerrit patch submissions fail without a Change-Id because the review system requires this identifier to track revisions. You must install the Gerrit commit-msg hook to automatically append the Change-Id to your commits before pushing.

What is the standard workflow for TYPO3 core code review?▼

The standard workflow for TYPO3 core code review involves creating a patch, pushing it to Gerrit, and tracking the review process until acceptance. It covers the end-to-end process from linking forge issues to documenting changes upon successful review.

Do I need a TYPO3.org account to contribute to the core repository?▼

Yes, you need a TYPO3.org account to contribute to the core repository. The contribution workflow requires this account to generate Gerrit authentication keys and properly submit patches for review by the TYPO3 development team.

Can I use my standard Git workflow for TYPO3 core contributions?▼

You cannot use a standard Git workflow for TYPO3 core contributions without modifications. You must configure specific Gerrit remotes, enforce Change-Id commits, and apply standardized branch handling to align with TYPO3 development practices.

Related Skills

Explore More Software Engineering Skills→
MicrockMicrock
322

gerrit

Configure Gerrit remotes and submit code reviews via JSON payloads.

Community
Advanced
netresearchnetresearch
51

typo3-core-contributions

Guide TYPO3 Core contributors through Gerrit-based patch submission and commit message standards.

Official
Advanced
wikimediawikimedia
4

review-patch

Fetch a Gerrit change by ID and generate a structured code review.

Official
Intermediate
odyssey4meodyssey4me
12

gerrit

Manage Gerrit code reviews via git-review CLI and SSH commands.

Community
Intermediate