v2.0.0

Breaking Changes

• Renamed templates/ to assets/ - Following skill-creator conventions, the templates/ directory has been renamed to assets/. Update any references in your workflows or documentation.

Improvements

• Rewritten SKILL.md - Now uses imperative/trigger-based writing style per skill-creator guidelines
• Complete documentation - All 15 references, 11 scripts, and 1 asset template are now fully documented
• Fixed non-existent script reference - Removed watch_docs.sh from documentation (script doesn't exist)
• Updated internal references - All path references in add-agents-md.sh and README.md updated

Migration

Update any paths from:

templates/AGENTS.md

To:

assets/AGENTS.md

v1.9.3

Reduced SKILL.md size from 12,990 to 3,505 bytes (73% reduction) for context efficiency

v1.9.2

Fix skills path format for Claude Code compatibility

v1.9.1

Changes

• Restructured skill for Claude Code compatibility
• Skill files now in skills/typo3-docs/ subdirectory
• Fixes installation issues in Claude Code plugin system

This is a structural change with no functional differences.

v1.9.0

What's changed

Added

• Claude Code plugin structure (plugin.json, .claude-plugin/)

Full Changelog: v1.8.0...v1.9.0

v1.8.0

What's Changed

Documentation improvements

• Prefer literalinclude for complete code examples - Updated guidance to use literalinclude as the preferred method for code blocks of 5+ lines
• File naming convention - Added underscore prefix convention for code snippet files (_ClassName.php, _config.yaml)
• File organization - Documented recommended structure for storing code snippets alongside RST files
• Text markers - Added examples for :start-after: and :end-before: options for maintainable line selection
• Updated decision guide - Clear guidance on when to use literalinclude vs code-block
• Pre-commit checklist - Updated to prioritize literalinclude usage

Benefits of literalinclude

• IDE support for syntax validation
• Reusability across multiple documentation pages
• Single source of truth for code examples
• Testability of code snippets

v1.7.0

What's New

Content & Structure Documentation

• Content directives guide - Comprehensive reference for accordion, admonitions, cards, tabs, tables, version directives, and viewhelpers
• Code structure elements guide - Complete reference for code-block, literalinclude, confval, PHP domain, and site settings
• Coding guidelines - .editorconfig enforcement, formatting rules, heading hierarchy

Workflow Improvements

• Init command workflow - Use docker ... init when creating documentation from scratch
• Live-view watch mode - Real-time preview with --watch flag documentation
• Screenshot guide - Docker container setup, image requirements, proactive suggestions

Other Enhancements

• Version-agnostic description (docs.typo3.org standards, not TYPO3 13.x)
• Enhanced guides.xml reference with GitHub integration extraction
• File structure requirements and reference
• Architecture Decision Records (ADR) documentation
• Visual verification step in workflow
• Expanded pre-commit checklist (now 15 items)

Full Changelog

v1.6.1...v1.7.0

v1.6.1

What's changed

Fixed

• Concise composer.json description, update email to info@netresearch.de

Full Changelog: v1.6.0...v1.6.1

v1.6.0

What's changed

Added

• Warning about committing Documentation-GENERATED-temp
• Standardized installation, composer.json, release workflow

Full Changelog: v1.5.3...v1.6.0

v1.5.3 - guides.xml modernization

Changes

• Prefer guides.xml (modern PHP-based rendering) over Settings.cfg (legacy Sphinx-based)
• Add webhook status codes to intercept-deployment.md:
  • 200 - ping success
  • 204 - push accepted
  • 412 - precondition failed (expected on first-time)
• Add GitHub CLI automation examples for webhook setup
• Fix validate_docs.sh to accept either guides.xml OR Settings.cfg
• Update templates/AGENTS.md with complete guides.xml configuration example
• Update typo3-extension-architecture.md documentation requirements

Migration Note

New extensions should use guides.xml (modern PHP-based rendering). Existing extensions with Settings.cfg should consider migrating to guides.xml for improved rendering capabilities.