Integration test design toolkit: discover a project's test conventions and how integration tests are separated (conventions), assess the quality of existing tests for over-mocking and misleading coverage (critique), find state-establishment and teardown affordances (state), and synthesize a prioritized scenario plan from confirmed customer journeys and documented requirements (design). Reports conflicts between what the documentation requires and what the code does. Read-only discovery; requires the profile plugin.
Plugin itest from marketplace efitz-skills in ericfitz/skills. Commands read from the repo's manifest — 8 days ago.
conventionsDetermine 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.
critiqueAssess 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. Emi
designDesign 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 integratio
stateDiscover 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.
Dependency discovery toolkit: enumerate what a system depends on across six categories — packages, out-of-project services, configuration, secrets and permissions, OS and cloud resources, and network paths — each with the failure-relevant declarations (timeout, retry, fallback, health check) found for it. Static and read-only; emits a versioned JSON contract consumed by downstream analysis.
8 skills
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.
7 skills
Portable CATS API fuzzing toolkit: bootstrap per-repo config (init), run fuzz campaigns through config-declared shell hooks (run), query and render results from SQLite (report), triage true positives into a remediation plan (analyze), and manage declarative false-positive rules (fp). Repo-specific setup lives in .local/cats/config.yaml; false-positive rules live in a committed YAML file.
5 skills · 1 agent
Developer toolkit (sem-powered): annotate code with durable SEM@<sha> intent markers (sem-annotate), keep them maintained via a project convention (sem-auto), and find dead code + duplication and produce a ranked plan (dedupe). Uses the sem CLI entity graph. Supports Go, TypeScript/JavaScript, and Python.
3 skills · 3 agents
Logseq graph toolkit for a local classic (file-based) graph: capture notes/TODOs into journals or pages (capture), answer questions from the graph (query), find consistency problems (lint), merge/dedupe and restructure pages (organize), and import notes from an Obsidian vault (from-obsidian). Hybrid file/HTTP-API access with automatic graph discovery.
5 skills
Project discovery toolkit: identify what a codebase is built with (stack), what its requirements documents, PRDs, specs, and wiki pages say it must do (docs), how it deploys and what it depends on (topology), and what workflows its users actually perform (journeys). Read-only inference backed by a deterministic inventory script; emits versioned JSON contracts consumed by other plugins.
5 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Use Alibaba Open Code Review from local Codex.
2 skills
Claude Code skill for creating and presenting Slidev slidedecks
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.