Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

file-actions

Étoiles3

Forks0

Mis à jour5 mai 2026 à 17:58

File-action ID rules for viewer/editor/user-menu settings, parameterized commands, resolver behavior, and regression coverage. Use when changing file-action settings, direct dispatch, Edit New routing, or related specs/tests.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

RedSalamanders

RedSalamanders/RedSalamander

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	file-actions
description	File-action ID rules for viewer/editor/user-menu settings, parameterized commands, resolver behavior, and regression coverage. Use when changing file-action settings, direct dispatch, Edit New routing, or related specs/tests.

file-actions

Core contract

File-action IDs preserve their configured casing when saved and displayed.
All file-action ID comparisons are case-insensitive.
IDs must be unique case-insensitively within each action list.
IDs that differ only by case are invalid duplicates and must be rejected by settings validation.
Association references and parameterized command IDs (cmd/pane/viewWith/<id>, cmd/pane/editWith/<id>, cmd/pane/userMenu/<id>) resolve case-insensitively.
When lookup succeeds, downstream UI/runtime behavior should use the matched action definition rather than the caller-supplied casing.

Change checklist

Update settings-store validation and lookup together.
Update runtime resolver and direct-dispatch call sites together.
Keep preferences/action-status helpers aligned with the same case-insensitive lookup rule.
Add focused selftests for:
- persisted round-trip or no-recovery load success when references differ only by case
- malformed-settings rejection for duplicate IDs that differ only by case
- parameterized command dispatch with mixed-case configured IDs
Update the authoritative docs:
- Specs/Core/Core_SettingsStore.md
- Specs/SettingsStore.schema.json
- Specs/UI/UI_CommandMenuKeyboard.md
- Specs/Testing/Testing_TestCoverage.md

Plus depuis ce dépôt

même dépôt

localization

RedSalamanders/RedSalamander

Localization and resource management for Windows RC files. Use when adding user-facing strings, creating menus, working with STRINGTABLE, or using LoadStringResource and FormatStringResource helpers.

2026-06-073

compiler-warnings

RedSalamanders/RedSalamander

Compiler warning policy and suppression patterns for MSVC /Wall. Use when fixing warnings, adding pragma suppressions, or dealing with C4365, C5219, C4625, C4626 and other compiler diagnostics.

2026-05-113

cpp-build

RedSalamanders/RedSalamander

Build RedSalamander C++ project using PowerShell build script. Use when building, compiling, or rebuilding the solution or specific projects like RedSalamander, RedSalamanderMonitor, Common, or FileSystem.

2026-05-063

skill-name

RedSalamanders/RedSalamander

{what this skill teaches agents}

2026-05-063

async-threading

RedSalamanders/RedSalamander

Threading model and async operation patterns for Windows applications. Use when implementing background operations, thread synchronization, posting to UI thread, or using thread pools.

2026-04-293

cpp-modern-style

RedSalamanders/RedSalamander

Modern C++23 coding style and conventions for RedSalamander. Use when writing new code, reviewing style, using STL containers, smart pointers, std::format, std::optional, or following naming conventions.

2026-04-293

name	file-actions
description	File-action ID rules for viewer/editor/user-menu settings, parameterized commands, resolver behavior, and regression coverage. Use when changing file-action settings, direct dispatch, Edit New routing, or related specs/tests.

file-actions

Core contract

File-action IDs preserve their configured casing when saved and displayed.
All file-action ID comparisons are case-insensitive.
IDs must be unique case-insensitively within each action list.
IDs that differ only by case are invalid duplicates and must be rejected by settings validation.
Association references and parameterized command IDs (cmd/pane/viewWith/<id>, cmd/pane/editWith/<id>, cmd/pane/userMenu/<id>) resolve case-insensitively.
When lookup succeeds, downstream UI/runtime behavior should use the matched action definition rather than the caller-supplied casing.

Change checklist

Update settings-store validation and lookup together.
Update runtime resolver and direct-dispatch call sites together.
Keep preferences/action-status helpers aligned with the same case-insensitive lookup rule.
Add focused selftests for:
- persisted round-trip or no-recovery load success when references differ only by case
- malformed-settings rejection for duplicate IDs that differ only by case
- parameterized command dispatch with mixed-case configured IDs
Update the authoritative docs:
- Specs/Core/Core_SettingsStore.md
- Specs/SettingsStore.schema.json
- Specs/UI/UI_CommandMenuKeyboard.md
- Specs/Testing/Testing_TestCoverage.md