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-composer.sh
View on GitHub#!/usr/bin/env bash
# SPDX-License-Identifier: MIT
# SPDX-FileCopyrightText: Netresearch DTT GmbH
#
# Extract Composer Dependencies
#
# Extracts dependency information from composer.json
#
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"
COMPOSER_FILE="${PROJECT_DIR}/composer.json"
OUTPUT_FILE="${DATA_DIR}/dependencies.json"
mkdir -p "${DATA_DIR}"
if [ ! -f "${COMPOSER_FILE}" ]; then
echo -e "${YELLOW}No composer.json found, skipping${NC}"
echo '{"dependencies": {}}' > "${OUTPUT_FILE}"
exit 0
fi
echo "Extracting composer.json..."
# Extract relevant sections using jq if available, otherwise use PHP
if command -v jq &> /dev/null; then
jq '{
extraction_date: now | todate,
name: .name,
description: .description,
type: .type,
require: .require,
"require-dev": (."require-dev" // {}),
autoload: .autoload,
scripts: (.scripts // {})
}' "${COMPOSER_FILE}" > "${OUTPUT_FILE}"
else
# Fallback to PHP. The path is passed as an argument: interpolated into
# the PHP source, a directory name with a single quote was a syntax error.
# shellcheck disable=SC2016 # the $ signs belong to PHP, not to the shell
php -r '
$data = json_decode(file_get_contents($argv[1]), true);
echo json_encode([
"extraction_date" => date("c"),
"name" => $data["name"] ?? "",
"description" => $data["description"] ?? "",
"type" => $data["type"] ?? "",
"require" => $data["require"] ?? [],
"require-dev" => $data["require-dev"] ?? [],
"autoload" => $data["autoload"] ?? [],
"scripts" => $data["scripts"] ?? []
], JSON_PRETTY_PRINT | JSON_UNESCAPED_SLASHES);
' "${COMPOSER_FILE}" > "${OUTPUT_FILE}"
fi
echo -e "${GREEN}✓ composer.json extracted: ${OUTPUT_FILE}${NC}"
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 |