agentsclimarketplace

Typo3 core contributions

Skill netresearch/typo3-core-contributions-skill/skills/typo3-core-contributions

Agent Skill for TYPO3 Core contributions - Gerrit workflow, CI/CD, quality automation | Claude Code compatible

Install
npx -y skills add netresearch/typo3-core-contributions-skill --skill typo3-core-contributions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when analyzing TYPO3 Forge issues, submitting patches to Gerrit, contributing core bug fixes, documentation contributions, cherry-pick workflows, or CI debugging on Gerrit. Core `main` branch is v15-in-progress (PHP 8.4/8.5); v14.3 LTS bugfixes land on branch `14.3` and are backported via cherry-pick. Also triggers on: forge.typo3.org, core patch, Gerrit review, TYPO3 Core contribution.

SKILL.md

3.9 KB, 978 tokens by cl100k_base, as published. Nobody here has run it

TYPO3 Core Contributions

Guide for contributing to TYPO3 Core: Forge issues, Gerrit patches, CI debugging, and review workflows.

When to Use

  • Forge issue analysis or creation (forge.typo3.org/issues/*)
  • Patch submission, CI debugging, Gerrit review workflow
  • Commit message formatting, cherry-picks, rebasing

Prerequisites

Run ${CLAUDE_SKILL_DIR}/scripts/verify-prerequisites.sh to check: TYPO3.org account, Gerrit SSH (ssh -p 29418 <user>@review.typo3.org), Git email matching Gerrit. See references/account-setup.md.

Workflow

  1. Setup: Account + environment (${CLAUDE_SKILL_DIR}/scripts/setup-typo3-coredev.sh, references/ddev-setup-workflow.md)
  2. Branch: git checkout -b feature/<issue>-description
  3. Analyze: Understand root cause, reproduction steps, affected versions before coding
  4. Develop: Implement fix + tests, validate with typo3-conformance-skill
  5. Commit: Follow format below, include Resolves: #<issue> + Releases:
  6. Push: git push origin HEAD:refs/for/main (starts as WIP)
  7. CI: Wait for all jobs. Read actual GitLab logs at git.typo3.org/typo3/CI/cms/-/jobs/<id>. Fix ALL failures in one amend+push
  8. Ready: Mark ready via git push origin HEAD:refs/for/main%ready or Gerrit UI "Start Review"
  9. Review: Address feedback, amend commit, preserve Change-Id. Fetch reviewer's patchset first to preserve their message edits: git fetch origin refs/changes/XX/NNNNN/N && git reset --soft FETCH_HEAD
  10. Update: git commit --amend && git push origin HEAD:refs/for/main

Commit Format

[TYPE] Subject (imperative mood, max 52 chars)

How and why (not what). Wrap at 72 chars.

Resolves: #12345
Releases: main, 13.4, 12.4

Types: [BUGFIX], [FEATURE] (main only), [TASK], [DOCS], [SECURITY] Breaking: [!!!][TYPE] prefix, Releases: main only Required: Every commit MUST have Resolves: (not just Related:)

CI Debugging

Read ALL failing job logs (never guess). Common jobs: cgl pre-merge (code style), phpstan (static analysis), unit/functional (tests). Fix all in one patchset. Local checks:

./Build/Scripts/runTests.sh -s unit && ./Build/Scripts/runTests.sh -s functional
./Build/Scripts/cglFixMyCommit.sh
./Build/Scripts/runTests.sh -s phpstan

Key Operations

TaskCommand
Push to Gerritgit push origin HEAD:refs/for/main
Mark readygit push origin HEAD:refs/for/main%ready
Set WIPgit push origin HEAD:refs/for/main%wip
Rebasegit fetch origin && git rebase origin/main
Cherry-pick patchgit fetch origin refs/changes/XX/NNNNN/N && git cherry-pick FETCH_HEAD
Install hookcp Build/git-hooks/commit-msg .git/hooks/ && chmod +x .git/hooks/commit-msg
Fix email mismatchGIT_COMMITTER_EMAIL="registered@email" git commit --amend --no-edit
Forge API${CLAUDE_SKILL_DIR}/scripts/create-forge-issue.sh, references/forge-api.md

References

TopicFile
Account setupreferences/account-setup.md
Commit formatreferences/commit-message-format.md
Gerrit workflowreferences/gerrit-workflow.md
Review patternsreferences/gerrit-review-patterns.md
Modern patternsreferences/modern-typo3-patterns.md
DDEV setupreferences/ddev-setup-workflow.md
Forge APIreferences/forge-api.md
Commit hookreferences/commit-msg-hook.md
Troubleshootingreferences/troubleshooting.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.