netresearch/typo3-docs-skill / skills/typo3-docs
typo3-docs
FlaggedUse when TYPO3 extension documentation has to render on docs.typo3.org, which builds a manual from Documentation/guides.xml and reads no Settings.cfg (a single README.rst serves an extension too small for one): when an extension has no documentation yet, or when creating, editing or reviewing Documentation/*.rst, guides.xml, README.md or XLF translations, rendering docs with Docker, TYPO3 RST directives, screenshots, or XLIFF 2-space indentation (TYPO3 v14+).
scripts/extract-extension-config.sh
View on GitHub#!/usr/bin/env bash
# SPDX-License-Identifier: MIT
# SPDX-FileCopyrightText: Netresearch DTT GmbH
#
# Extract Extension Configuration
#
# Extracts metadata and configuration from:
# - ext_emconf.php (extension metadata)
# - ext_conf_template.txt (configuration options)
#
set -e
# Colors
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m'
# Configuration
PROJECT_DIR="$(pwd)"
DATA_DIR="$(bash "$(dirname "${BASH_SOURCE[0]}")/extraction-dir.sh")/data"
# shellcheck source=SCRIPTDIR/json-string.sh
. "$(dirname "${BASH_SOURCE[0]}")/json-string.sh"
EXT_EMCONF="${PROJECT_DIR}/ext_emconf.php"
EXT_CONF_TEMPLATE="${PROJECT_DIR}/ext_conf_template.txt"
mkdir -p "${DATA_DIR}"
# Extract ext_emconf.php
if [ -f "${EXT_EMCONF}" ]; then
echo "Extracting ext_emconf.php..."
OUTPUT_FILE="${DATA_DIR}/extension_meta.json"
# Use PHP to parse ext_emconf.php properly. This runs the file's PHP.
# The path is passed as an argument: interpolated into the PHP source, a
# directory name with a single quote was a PHP syntax error.
# shellcheck disable=SC2016 # the $ signs belong to PHP, not to the shell
php -r '
$_EXTKEY = "temp";
include $argv[1];
echo json_encode([
"extraction_date" => date("c"),
"metadata" => $EM_CONF[$_EXTKEY] ?? []
], JSON_PRETTY_PRINT | JSON_UNESCAPED_SLASHES);
' "${EXT_EMCONF}" > "${OUTPUT_FILE}"
echo -e "${GREEN}✓ ext_emconf.php extracted: ${OUTPUT_FILE}${NC}"
else
echo -e "${YELLOW}No ext_emconf.php found, skipping${NC}"
fi
# Extract ext_conf_template.txt
if [ -f "${EXT_CONF_TEMPLATE}" ]; then
echo "Extracting ext_conf_template.txt..."
OUTPUT_FILE="${DATA_DIR}/config_options.json"
# Parse ext_conf_template.txt format:
# # cat=category/subcategory; type=type; label=Label: Description
# settingName = defaultValue
{
echo '{'
printf ' "extraction_date": "%s",\n' "$(date -u +"%Y-%m-%dT%H:%M:%SZ")"
echo ' "config_options": ['
} > "${OUTPUT_FILE}"
first=true
while IFS= read -r line; do
# Check if comment line with metadata
if [[ $line =~ ^#\ cat= ]]; then
# Extract metadata from comment
category=$(echo "$line" | sed -n 's/.*cat=\([^/;]*\).*/\1/p')
subcategory=$(echo "$line" | sed -n 's/.*cat=[^/]*\/\([^;]*\).*/\1/p')
type=$(echo "$line" | sed -n 's/.*type=\([^;]*\).*/\1/p')
label_and_desc=$(echo "$line" | sed -n 's/.*label=\(.*\)/\1/p')
label=$(echo "$label_and_desc" | cut -d':' -f1)
description=$(echo "$label_and_desc" | cut -d':' -f2- | sed 's/^ *//')
# Check for WARNING in description
security_warning=""
if echo "$description" | grep -qi "WARNING:"; then
security_warning=$(echo "$description" | sed -n 's/.*WARNING: \(.*\)/\1/p')
description=$(echo "$description" | sed 's/WARNING:.*//' | sed 's/ *$//')
fi
# Read next line for setting name and default. At the end of the
# file read returns 1, which set -e would turn into an exit in the
# middle of the JSON. It still assigns a last line that has no
# newline, so keep that value; after a comment on the last line it
# is empty.
read -r next_line || true
if [[ $next_line =~ ^([^=]+)\ =\ (.+)$ ]]; then
setting_name="${BASH_REMATCH[1]}"
setting_name="${setting_name%"${setting_name##*[! ]}"}"
default_value="${BASH_REMATCH[2]}"
default_value=$(echo "$default_value" | sed 's/^ *//;s/ *$//')
# Write JSON entry, with a comma before every entry but the first
{
if [ "$first" = false ]; then
echo ' ,'
fi
echo ' {'
printf ' "key": %s,\n' "$(json_string "$setting_name")"
printf ' "category": %s,\n' "$(json_string "$category")"
printf ' "subcategory": %s,\n' "$(json_string "$subcategory")"
printf ' "type": %s,\n' "$(json_string "$type")"
printf ' "label": %s,\n' "$(json_string "$label")"
printf ' "description": %s,\n' "$(json_string "$description")"
printf ' "default": %s\n' "$(json_string "$default_value")"
if [ -n "$security_warning" ]; then
echo ' ,'
printf ' "security_warning": %s\n' "$(json_string "$security_warning")"
fi
echo -n ' }'
} >> "${OUTPUT_FILE}"
first=false
fi
fi
done < "${EXT_CONF_TEMPLATE}"
# Close JSON
{
echo
echo ' ]'
echo '}'
} >> "${OUTPUT_FILE}"
echo -e "${GREEN}✓ ext_conf_template.txt extracted: ${OUTPUT_FILE}${NC}"
else
echo -e "${YELLOW}No ext_conf_template.txt found, skipping${NC}"
fi
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |