Plugin Claude Code
Plugin marketplace listing 1 plugin: dev-skills.
Plugin Claude Code
Plugin marketplace listing 1 plugin: dev-skills.
Plugin Claude Code
Autonomous dev workflow in one plugin: 32 skills (wayfinder mapping, design, api design, openapi spec, human-friendly docs, mermaid diagrams, github actions, ui prototype, throwaway prototype, plan, implement, TDD, e2e testing, smoke testing, review, QA, debug, refactor, perf, release, clean up, git safety…
Settings file Claude Code
Agent settings declaring 52 allowed tools.
Instructions file
Claude Code instructions for amjadjibon/skills, covering claude.md, repository purpose, structure, skill.md format and skill content here.
Command
Run the autonomous dev-loop orchestrator — plan → review plan → implement → QA → code review → fix, iterating until the review passes; pauses for approval before pushing.
Hook
Runs when a session starts on startup, executing auto-install.sh via bash. From amjadjibon/skills.
Skill Claude CodeCodex
REST/GraphQL design — resource/URL shape, pagination, versioning, HATEOAS, localization, GraphQL schema-first/DataLoader/Relay. Trigger on "design this API", "REST or GraphQL", "version/localize this API", "review this API design". For the OpenAPI document itself, use openapi-spec.
Skill Claude CodeCodex
Ultra-compressed output. Drop articles, filler, pleasantries, hedging, and tool-call narration; keep every technical fact, exact symbol, and error string. Use on "caveman", "caveman mode", "be brief", "be terse", "less tokens", "stop explaining", "shorter answers", or when responses run too long.
Skill Claude CodeCodex
Housekeeping — delete merged local and remote branches, prune stale tracking refs, close resolved GitHub issues, remove leftover worktrees. Use on "clean up", "prune branches", "remove merged branches", "close issues", "tidy up", "housekeeping".
Skill Claude CodeCodex
Review a diff, branch, or PR for correctness bugs, security issues, and simplification opportunities; findings to .spec/ /REVIEW.md. Trigger on "review this", "code review", "security review", "audit this", or after something is implemented and needs checking before merge.
Skill Claude CodeCodex
Write .spec/ /PLAN.md with phased, checkbox-driven steps for a feature, refactor, upgrade, or infrastructure change. Trigger on "create/make a plan", "plan this feature/refactor/upgrade", any request to document steps before coding, and proactively when complexity warrants a written plan.
Skill Claude CodeCodex
Systematically debug a failing test, error, or unexpected behavior — reproduce, isolate root cause, fix minimally, verify. Use on "debug", "fix this bug", "it's broken", "this is failing", "why is this happening", or a shared error message, stack trace, or failing test output.
Skill Claude CodeCodex
Decide a feature's shape before planning — system design, data model, API contract, UI/UX, whichever apply — and write .spec/ /DESIGN.md. Trigger on "design this feature/API/schema/UI", "how should we structure this", or between dev-research and dev-create-plan.
Skill Claude CodeCodex
Write documentation someone will actually read — READMEs, guides, API references, runbooks — short, scannable, example-first, and verified against the code. Trigger on "write docs", "document this", "write a README", "explain how to use this", "our docs are too long/confusing", or a doc that needs rewriting for humans.
Skill Claude CodeCodex
Write and maintain Playwright end-to-end tests that drive the whole system through its real UI/API — setup, fixtures, test independence, flake handling, CI wiring. Trigger on "write e2e tests", "set up Playwright", "test the full user flow", "our e2e tests are flaky", or when tests/e2e needs work.
Skill Claude CodeCodex
Execute an implementation plan from .spec/ /PLAN.md — tick checkboxes, commit each phase. Trigger on "implement/execute/continue/resume the plan", "start phase 1", "go" right after a plan was created, or whenever there is a PLAN.md to build, even if the user never says "plan".
Skill Claude CodeCodex
Run an autonomous plan → implement → review loop for a feature, iterating until the code review passes and pausing for approval before pushing. Use on "loop on this", "keep going until it passes review", "autonomous dev loop", "plan implement and review", or a self-correcting agent workflow.
Skill Claude CodeCodex
Profile, optimize, and benchmark performance — measure baseline first, find the real bottleneck, optimize one thing at a time, prove it with numbers. Use on "it's slow", "optimize this", "improve performance", "reduce latency", "profile this", or shared timing/benchmark output.
Skill Claude CodeCodex
Repo-wide over-engineering scan — the whole tree instead of a diff, ranked by what to delete, simplify, or replace with a stdlib/native equivalent. Use on "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find the bloat", "where is this over-built". Reports; applies nothing.
Skill Claude CodeCodex
Harvest every TODO/FIXME marker into one ledger with ceiling, trigger, owner, and age, flagging the ones that name no trigger. Use on "ponytail debt", "yagni debt", "what did we defer", "list the shortcuts", "collect the TODOs", "TODO ledger". Reports; changes no code.
Skill Claude CodeCodex
Review a diff or branch for over-engineering only — reinvented stdlib, dependencies the platform covers, one-implementation abstractions, dead flexibility, code that shrinks. Use on "review for over-engineering", "is this over-engineered", "what can we delete", "simplify review". Correctness, security, and performance…
Skill Claude CodeCodex
Build the smallest thing that works — question whether the code needs to exist, reuse what the repo has, stdlib over a dependency, native platform over a library, one line over fifty. Use on any coding task, and on "ponytail", "be lazy", "yagni", "keep it simple", "minimal solution", "don't over-engineer", or…
Skill Claude CodeCodex
Analyse test coverage, identify untested paths, write the missing tests (unit, integration, e2e), and produce a QA report. Use on "QA this", "write tests", "improve test coverage", "add tests for", "test this feature", "what's not tested", or a quality gate before release.
Skill Claude CodeCodex
Refactor existing code without changing behavior — extract functions, reduce duplication, simplify logic, improve naming, against a test baseline taken before and verified after. Use on "refactor this", "clean up", "simplify", "extract", "reduce duplication", "improve naming", or a request for structural improvement…