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/check-settings-documented.sh
View on GitHub#!/usr/bin/env bash
# SPDX-License-Identifier: MIT
# SPDX-FileCopyrightText: Netresearch DTT GmbH
#
# TD-52: every setting the extension declares is mentioned in the documentation.
#
# The denominator comes from the code, not from a page count: ext_conf_template.txt
# says how many settings exist, so a three-setting extension can score full marks.
# Mentioned anywhere counts — using `confval` is better (typed, linkable) but is a
# recommendation, not the bar. Measured over the netresearch t3x fleet, this ranges
# from 0% to 100%, and one repo documents its settings in a backend module rather
# than in prose, which is why the check asks for a mention rather than a directive.
set -euo pipefail
[ -f ext_conf_template.txt ] || exit 0
[ -d Documentation ] || exit 0
missing=""
count=0
while IFS= read -r key; do
count=$((count + 1))
# A direct file grep, never `printf … | grep -q`: that pipeline inverts under
# pipefail once the input passes the pipe buffer.
if ! grep -rqF -- "$key" Documentation/ 2>/dev/null; then
missing="$missing $key"
fi
done < <(sed -e 's/#.*$//' ext_conf_template.txt \
| grep -oE '^[A-Za-z][A-Za-z0-9_.]*[[:space:]]*=' \
| sed -e 's/[[:space:]]*=$//' | sort -u)
[ "$count" -eq 0 ] && exit 0
[ -z "$missing" ] && exit 0
echo "Settings declared in ext_conf_template.txt but not mentioned in Documentation/:$missing"
echo " ($count declared; document each one, ideally as a confval so it is typed and linkable)"
exit 1
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 |