Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

validate-i18n

Sterne0

Forks2

Aktualisiert26. Mai 2026 um 18:08

Run the i18n validation script to check for missing, extra, or misformatted translation keys before publishing

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

lbruton

lbruton/SpecFlow

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	validate-i18n
description	Run the i18n validation script to check for missing, extra, or misformatted translation keys before publishing

Run the i18n validator for the specflow project:

cd /Volumes/DATA/GitHub/specflow && node scripts/validate-i18n.js

Report the full output. If clean, confirm "i18n validation passed — all translation keys are consistent."

If there are failures, list them clearly grouped by:

Missing keys (present in one locale but not another)
Extra keys (not used in source)
Format mismatches (e.g., interpolation variable differences)

Suggest fixes for any issues found.

Mehr aus diesem Repository

gleiches Repository

spec

lbruton/SpecFlow

Spec-driven development orchestrator. Creates and executes spec-workflow specifications from an issue — Requirements → Design → Tasks → Implementation with dashboard approvals and subagent dispatch.

2026-06-050

audit

lbruton/SpecFlow

On-demand project health check — code quality (CGC), security (Codacy SRM), instruction file drift (CLAUDE.md vs Agents.md vs Gemini.md), issue landscape, index health. Triggers: "audit", "health check", "check project health", "scan codebase", "code health", "instruction drift", "check for drift".

2026-05-260

chat

lbruton/SpecFlow

Casual, freeform discovery mode (Phase 0 of the Spec Flow Lifecycle). Explore an idea without committing to code, issues, or specs. Dispatch subagents for research, surface past work from mem0, and build context until the idea is ready for an issue and formal spec. Triggers on "/chat", "/talk", "let's explore", "I have an idea", "what if we".

2026-05-260

discover

lbruton/SpecFlow

Structured brainstorm and research phase (Phase 1 of the Spec Flow Lifecycle). Takes an issue ID, dispatches research agents, runs codebase analysis, and produces a Discovery Brief with all open questions resolved. Bridges the gap between casual exploration (/chat) and formal spec creation (/spec). Triggers on "/discover", "/brainstorm", "research this issue", "explore this before we spec it".

2026-05-260

issue

lbruton/SpecFlow

Issue management — create, read, update, list. Backend is driven by `.specflow/config.json` `issue_backend` field: `plane` (Plane MCP, primary going forward) or `docvault` (legacy markdown — for projects not yet migrated). Triggers on: "create issue", "issue", "new issue", "new bug", "file a bug", "track this".

2026-05-260

migrate-skill

lbruton/SpecFlow

Migrate a user-level skill into the specflow plugin's skills directory. Use when porting a proven skill from ~/.claude/skills/ to the plugin for distribution. Covers generic vs project-specific classification, MCP prompt extraction, deprecation of user-level shims, and verification.

2026-05-260

Jeden Skill mit einem Klick ausführen