starter-kit-full

Plugin starter-kit-full from marketplace claude-code-starter-kit in sharklandy/claude-code-starter-kit. Commands read from the repo's manifest — 1 month ago.

Skills (21)

• code-review

  Perform a structured code review of a diff, pull request, or any non-trivial change before it is merged or committed. Trigger on any request to review code, review a diff/PR, or before any non-trivial commit.

• test-strategy

  Decide what to test and at what level, and detect fragile existing tests. Trigger when asked what to test, how to structure a test suite, whether a test belongs at the unit/integration level, or when reviewing existing tests for reliability — not for generating test code directly.

• adversarial-code-review

  Challenge a code diff with a fresh-context adversarial reviewer looking for bugs, obvious security flaws, regressions, and dead code. Trigger before merging any non-trivial diff, or whenever asked for a second opinion / adversarial review / "fresh eyes" on a change.

• avoid-agentic-pitfalls

  Apply on virtually any non-trivial coding task, regardless of domain or stack. Enforces discipline against silent unverified assumptions, over-engineering, and out-of-scope edits. Trigger on any substantial code change, not just specific cases.

• bug-triage-runbook-template

  Diagnose and categorize incoming user feedback or bug reports. Trigger whenever processing a message from <TODO: nom du canal ou de la source des retours, ex. #feedback>.

• changelog-from-commits

  Generate or update CHANGELOG.md from git history since the last tag or entry. Trigger whenever asked to prepare a release, update the changelog, or summarize changes since the last version.

• checkout-verifier-template

  Verify any change touching the checkout flow, payment form, or cart summary before declaring it done. Trigger on changes to <TODO: chemin des composants checkout>/**, <TODO: chemin des composants payment>/**, or any file importing your payment provider's SDK.

• choose-your-loop

  Help choose and validate the right Claude Code mechanism (turn-based prompt, /goal, dynamic workflow, or /loop /schedule routine) BEFORE writing the final prompt. Trigger whenever the user expresses intent to set up a /goal, a workflow, a routine, or more generally "automate this", "make Claude do t

• commit-message-quality

  Enforce clear, atomic commit messages before committing. Trigger whenever about to run `git commit`, or when asked to clean up / split a commit or commit history.

• dependency-update-check

  Check for breaking changes and codebase impact before bumping a dependency version. Trigger whenever asked to upgrade, update, or bump a package/library/dependency version.

• env-doctor

  Diagnose a broken local development environment: incompatible runtime versions, missing or conflicting dependencies, missing environment variables, or ports already in use. Trigger whenever a project fails to start, build, or install for reasons that look environmental rather than a code bug.

• library-reference-template

  Reference for using <TODO: nom de la librairie, CLI ou SDK, interne ou externe> correctly. Trigger whenever a task involves importing, configuring, or calling <TODO: nom du package ou de la commande>.

• new-feature-scaffold

  Scaffold a new feature consistently with existing project conventions. Trigger whenever starting a new feature, module, or component from scratch.

• pr-description-generator

  Generate a complete pull request description from a diff or commit range. Trigger whenever asked to open a PR, write a PR description, or summarize a branch's changes for review.

• python-to-ts-migration-template

  Reference for porting a legacy Python module to a new TypeScript service. Trigger whenever a task involves migrating a file under <TODO: chemin du dossier legacy, ex. /legacy/reports/**>.

• readme-generator

  Generate or incrementally update a project's README.md from an analysis of its structure, dependencies, scripts, tests and CI. Trigger whenever asked to write, generate, or update a README.

• safe-refactor

  Guardrail before any non-trivial refactor: confirm sufficient test coverage exists first. Trigger whenever asked to refactor, restructure, clean up, or rewrite existing code without changing its behavior.

• systematic-debugging

  Generic runbook to diagnose any bug or unexpected behavior. Trigger whenever asked to fix a bug, investigate an error, or explain why something isn't working — before proposing a fix.

• verify-code-change

  Verify any non-trivial code change before declaring it done: build, existing test suite, and linter must all pass. Trigger after any edit that touches source files, regardless of language or stack.

• verify-form-change

  Verify any form or input change end-to-end before declaring it done. Trigger this whenever a task touches a <form>, an input validation rule, or a submit handler.

• verify-frontend-change

  Verify any UI change end-to-end before declaring it done. Trigger whenever a task touches a component, page, button, form control, or any other visible frontend behavior.

Similar plugins