typo3-core-contributions
Use when analyzing TYPO3 Forge issues, submitting patches to Gerrit, or contributing documentation to TYPO3 Core.
Best use case
typo3-core-contributions is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when analyzing TYPO3 Forge issues, submitting patches to Gerrit, or contributing documentation to TYPO3 Core.
Teams using typo3-core-contributions should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/typo3-core-contributions/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How typo3-core-contributions Compares
| Feature / Agent | typo3-core-contributions | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when analyzing TYPO3 Forge issues, submitting patches to Gerrit, or contributing documentation to TYPO3 Core.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# TYPO3 Core Contributions Guide for TYPO3 Core contribution workflow from account setup to patch submission. ## When to Use - Forge issue URLs (e.g., `https://forge.typo3.org/issues/105737`) - Contributing patches, fixing TYPO3 bugs - Gerrit review workflow, rebasing, CI failures ## Prerequisites ```bash scripts/verify-prerequisites.sh ``` Check: TYPO3.org account, Gerrit SSH, Git config (email must match Gerrit!) ## Workflow Overview 1. **Setup**: Account → Environment (`scripts/setup-typo3-coredev.sh`) 2. **Branch**: `git checkout -b feature/105737-fix-description` 3. **Analyze Issue**: Understand deeply before coding (see below) 4. **Develop**: Implement, write tests, validate with typo3-conformance-skill 5. **Verify CI**: Run full test suite locally, ensure all checks pass 6. **Commit**: Follow format, include `Resolves: #<issue>` + `Releases:` 7. **Submit**: `git push origin HEAD:refs/for/main` (starts as WIP) 8. **CI Check**: Wait for Gerrit CI, fix ALL failures before marking ready 9. **Mark Ready**: Remove WIP state only when all CI jobs pass 10. **Update**: Amend + push (preserve Change-Id!) 11. **Verify Releases**: After approval, test in all target branches ## Phase 3: Analyze Issue Deeply **Before writing any code**, thoroughly understand the problem: 1. **What is broken?** - Identify the exact behavior vs expected behavior 2. **Why is it broken?** - Trace the root cause in the codebase 3. **Reproduction steps** - Document minimal steps to reproduce 4. **Affected versions** - Check which branches have the issue (main, 13.4, 12.4) 5. **Related code** - Review existing tests and similar implementations 6. **Edge cases** - Consider what else might be affected **This analysis prevents wasted time** on incomplete fixes or patches that don't address the actual problem. ## Phase 5 & 8: CI Verification **Before marking ready for review**: 1. Run tests locally: `./Build/Scripts/runTests.sh -s unit && ./Build/Scripts/runTests.sh -s functional` 2. Check code style: `./Build/Scripts/cglFixMyCommit.sh` 3. Run PHPStan: `./Build/Scripts/runTests.sh -s phpstan` 4. After push: Wait for ALL Gerrit CI jobs to complete 5. **Read actual job logs** for any failures - never guess! 6. Fix ALL issues in one patchset before marking ready See `references/gerrit-workflow.md` for CI debugging details. ## Phase 11: Verify in Target Branches **After receiving +2 approval**, before merge: 1. Check your `Releases:` line (e.g., `main, 13.4, 12.4`) 2. Cherry-pick to each target branch locally 3. Verify fix works on each version 4. Ensure no version-specific issues (API differences, etc.) This prevents broken backports and ensures the fix works everywhere it's needed. ## Commit Format ``` [TYPE] Subject line (imperative, max 52 chars) Description explaining how and why. Resolves: #12345 Releases: main, 13.4, 12.4 ``` **Types**: `[BUGFIX]`, `[FEATURE]`, `[TASK]`, `[DOCS]`, `[SECURITY]`, `[!!!]` ## Related Skills - **typo3-ddev-skill**: Development environment - **typo3-testing-skill**: Test writing - **typo3-conformance-skill**: Code quality validation ## References | Topic | File | |-------|------| | Account setup | `references/account-setup.md` | | Commit format | `references/commit-message-format.md` | | Gerrit workflow | `references/gerrit-workflow.md` | | Troubleshooting | `references/troubleshooting.md` | --- > **Contributing:** https://github.com/netresearch/typo3-core-contributions-skill
Related Skills
devs:security-core
Comprehensive application security expertise covering authentication, authorization, OWASP Top 10, and security best practices. Use when (1) Implementing authentication (JWT, OAuth2, sessions, OAuth for CLI/TUI/desktop apps), (2) Adding authorization (RBAC, ABAC, RLS with Supabase/PostgreSQL), (3) Security auditing code or infrastructure, (4) Setting up security infrastructure (headers, CORS, CSP, rate limiting), (5) Managing secrets and credentials, (6) Preventing OWASP Top 10 vulnerabilities (injection, XSS, CSRF, etc.), (7) Reviewing code for security issues, (8) Configuring secure web applications in TypeScript, Python, or Rust. Automatically triggered when working with authentication/authorization systems, security reviews, or addressing security vulnerabilities.
core-tester
Comprehensive testing and quality assurance specialist for ensuring code quality through testing strategies
Axe-core Accessibility
Automated accessibility testing with axe-core and WCAG 2.1 compliance
author-contributions
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
solid-core-rendering
SolidJS rendering: render for client apps, hydrate for SSR, renderToString for server rendering, renderToStream for streaming, isServer checks.
rust-core
Comprehensive Rust development expertise covering core principles, patterns, error handling, async programming, testing, and performance optimization. Use when working on Rust projects requiring guidance on: (1) Language fundamentals (ownership, lifetimes, borrowing), (2) Architectural decisions and design patterns, (3) Web development (Axum, Actix-web, Rocket), (4) AI/LLM integration, (5) CLI/TUI applications, (6) Desktop development with Tauri, (7) Async/await and concurrency, (8) Error handling strategies, (9) Testing and benchmarking, (10) Performance optimization, (11) Logging and observability, or (12) Code reviews and best practices.
python-core
Create, write, build, debug, test, refactor, and optimize Python 3.10+ applications across all domains (data science, backend APIs, scripting, automation). Manage dependencies with uv (preferred), poetry, or pip. Implement type hints (typing module, generics, protocols), write tests with pytest (fixtures, parametrize, mocking), work with pandas DataFrames (creation, selection, groupby, merge), use dataclasses and decorators, handle errors with logging integration, and follow TDD workflows (Red-Green-Refactor). Configure virtual environments, pyproject.toml, and static analysis tools (mypy, pyright). Use when implementing Python features, fixing bugs, writing tests, managing packages, analyzing data, or building Python projects.
playwright-core
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, assertions, fixtures, network mocking, auth flows, debugging, and framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.
IFCore
Use when developing on the IFCore compliance checker. Covers contracts, check function conventions, issue reporting, app structure, and development patterns.
core-platform-notion-reviewer
Core Platform Team의 Notion 문서를 문서 타입(테크스펙/시스템설계/시스템소개/액션아이템/아이디어)과 17개 품질 기준에 따라 리뷰하고 개선안을 제안합니다. Notion MCP를 통해 문서 읽기/수정/검색을 수행합니다. 사용자가 Notion 문서 리뷰, 문서 품질 검사, Notion 페이지 개선 요청을 할 때 사용하세요.
core-life-ops
Core productivity workflows (daily planning, task triage, reporting) that work across any life domain. Not intended for direct use - imported by context-specific skills like covenant-marketing-ops or personal-life-ops.