Skill Claude CodeCodex
Generate and refresh SEM@ intent markers on code entities using the sem CLI. Use when the user asks to annotate code with SEM markers, add or refresh entity descriptions, or prepare a codebase for dedupe. Supports Go, TypeScript/JavaScript, and Python. Modes: full-scope, --update , --rebuild.
Skill Claude CodeCodex
Set up a project so SEM@ intent markers stay maintained — installs a SEM-marker convention block into the project's CLAUDE.md so Claude adds/updates markers as part of normal editing. Use when the user asks to enable sem markers for a project, set up sem-auto, or keep SEM markers fresh automatically.
Plugin Claude Code
Environment readiness toolkit: checks whether the CLI tools, config files, and auth sessions the other plugins depend on are present and working (check). Reports what's missing, why it matters, and how to fix it; report-only by default, with an explicit --fix mode that confirms and installs declared remedies for the…
Skill Claude CodeCodex
Check whether your environment is ready to use this marketplace's plugins — required CLI tools, config files, and auth sessions. Use when asked "is my environment ready", to check requirements, run an env check, or do a preflight before starting work. Reports hard failures, degraded (optional) capability loss, and…
Plugin Claude Code
GitHub workflow toolkit: pick the next issue to work on from a milestone/backlog (backlog) and file detailed issues into a repo/Project using a locally-provisioned metadata cache (create-issue). Use for issue triage and issue filing.
Hook
Runs when a session starts on startup, executing refresh_gh_projects.py via python3. From ericfitz/skills.
Skill Claude CodeCodex
Pick the next GitHub issue to work on. Use when the user asks what to work on next, requests the next backlog item, or wants an issue prioritized for the current milestone. Fetches open issues, applies exclusion rules, prioritizes by status/security/dependencies, and recommends one.
Skill Claude CodeCodex
Use when filing a GitHub issue (bug, feature, task, chore, etc.) against a repo, optionally adding it to a GitHub Project (v2), setting milestone from the current branch, and marking initial status. Reads all project/field/milestone IDs from the local cache (.local/gh-projects.json), provisioned by…
Plugin Claude Code
Integration test design toolkit: discover a project's test conventions (conventions), assess the quality of the tests it already has (critique), find its state-establishment affordances (state), and synthesize a full integration test design from customer journeys (design). Read-only discovery; requires the profile…
Skill Claude CodeCodex
Determine how tests are written and run in a project — frameworks, runner commands, how integration tests are separated from unit tests, house style, and reusable fixtures and helpers. Use before writing or designing tests in an unfamiliar codebase. Emits the itest:conventions contract.
Skill Claude CodeCodex
Assess the quality of a project's existing integration tests — finding over-mocking, implementation-detail assertions, non-determinism, shared state, and missing failure paths — and recommend keep, repair, replace, or delete for each. Use when auditing a test suite or before adding tests to one. Emits the…
Skill Claude CodeCodex
Design an integration test suite for a project — discovering its stack, its documented requirements, deployment shape, customer journeys, test conventions, existing-test quality, and state affordances, then synthesizing a prioritized scenario plan. Use when asked to design, plan, or scope integration tests, or to find…
Skill Claude CodeCodex
Discover how test state can be established in a project — writable data stores, factories and builders, seed tooling, test-only endpoints, ID generation, and teardown affordances. Use when planning test data setup or diagnosing test isolation problems. Emits the itest:state contract.
Plugin Claude Code
Localization/i18n toolkit: analyze missing keys, measure coverage, detect non-localizable strings, translate, validate translations, update JSON locale files, and backfill every locale. Use for i18n auditing, translation, and locale-file maintenance.
Skill Claude CodeCodex
Translate every missing or untranslated key across all i18n locale files using the master locale as the source. Tool-agnostic; reads project i18n configuration.
Skill Claude CodeCodex
Use when auditing i18n translation completeness across all target locales or identifying locales below a coverage threshold. Produces a per-locale and summary coverage report.
Skill Claude CodeCodex
Use when filtering localization keys, validating translation files, or deciding whether a string value should be translated or left as-is. Returns a boolean and the matched pattern.
Skill Claude CodeCodex
Use when translating UI strings, i18n values, or short localized content into a specific target language while preserving placeholders, formatting, capitalization, and tone.
Skill Claude CodeCodex
Use when modifying a JSON i18n file with additions, updates, or deletions while preserving formatting and writing atomically.
Skill Claude CodeCodex
Use when reviewing a translated string or validating an i18n file update, to verify placeholder preservation, length, encoding, and common translation errors.
Plugin Claude Code
Interact with a local classic (file-based) Logseq graph: capture notes/TODOs into journals or pages, answer questions from the graph, lint it for consistency, merge/restructure pages, and import notes from an Obsidian vault. Hybrid access: reads files directly, writes via the Logseq local HTTP API when the app is…
Skill Claude CodeCodex
Capture a note, TODO, or meeting summary into the user's local Logseq graph — today's journal by default, or a named page. Use when the user says "add this to Logseq", "log this in my journal", "note this down in Logseq", or wants a TODO captured.
Skill Claude CodeCodex
Convert and import notes from a local Obsidian vault into the user's Logseq graph — a single note, a folder, or the whole vault. Repeatable; already-imported unchanged notes are skipped. Use when the user asks to transfer, migrate, or import Obsidian notes into Logseq.
Skill Claude CodeCodex
Find consistency problems in the user's local Logseq graph — broken links, case-conflicting link spellings, orphan pages, near-duplicate page names, unparseable pages — and apply chosen fixes. Use when the user asks to lint, clean up, or check their Logseq graph for consistency.