All authors

Claude Skills by antoine-tena
github.com/antoine-tena24 skills0 installs0 views
- MigrationChange the Django database schema - one new numbered migration per change, never a rewrite of a merged migration. Use as soon as a model changes.Votes: 0GitHub stars: 2
- Postgres ReadSet up or repair the read-only access of the postgres MCP server to the local test database. Use when the postgres MCP server fails to connect, or after the test container was recreated.Votes: 0GitHub stars: 2
- Regen ApiRegenerate openapi.json and the frontend types after a change to a route or schema of the Django API (django-ninja). Use as soon as a schema or a route changes.Votes: 0GitHub stars: 2
- AdoptBring a repo that kiln did not generate under kiln (kiln adopt) - charter checked after each edit, docs/backlog/ tracking, repo visible in kiln status - on a branch merged afterwards into the integration branch. Use when the user asks to adopt kiln in an existing repo.Votes: 0GitHub stars: 2
- BacklogPick the next ticket from docs/backlog/backlog.md, add a ticket (bug, improvement, idea, task), record a ticket as started or done, or plan which tickets go into the next releases, in a repo that tracks its work this way. Use when the user asks what to do next, wants to note something to do or an idea, after starting or finishing a ticket, or when they ask what the next versions should contain.Votes: 0GitHub stars: 2
- CleanupRemove the worktrees and local branches already merged into the integration branch, and the leftovers (agent worktrees, orphan directories). Use when the user asks to clean up worktrees or branches.Votes: 0GitHub stars: 2
- ContributionHandle a pull request from an outside contributor, as a well-run open-source project would - safety check of the untrusted code, triage, review, then approve and merge with credit, ask for changes, finish it for them, or close it kindly; nothing is posted on GitHub without the user's yes. Use when a PR from someone else arrives on one of the user's repos, or when the user asks to look at, review, merge or answer a contributor's PR.Votes: 0GitHub stars: 2
- Good First IssuesKeep a small, steady stock of `good first issue` issues open on GitHub, drawn from the backlog and reserved for outside contributors, so a newcomer who wants to help always finds a task ready; nothing is posted without the user's yes. Use when the user asks for good first issues, wants to attract contributors, or when /kiln:contribution has just merged a PR that closed one.Votes: 0GitHub stars: 2
- MergeFinish a piece of work - the repo's checks on the branch, merge into the integration branch (develop), push, read GitHub's verdict on the merge, delete the branch (and its worktree). The full CI replayed on the machine only runs when a release goes out (/kiln:release).Votes: 0GitHub stars: 2
- ReleaseShip a release - a release/vN branch from develop, full checks (CI, migrations, contract, settings), the release announcement (what's-new window, email), merge into main tagged vN, deployment, merge back into develop. Use when the user asks to release, ship or deploy a version to production, or for an urgent production fix.Votes: 0GitHub stars: 2
- ReportReport a defect in what kiln provides (a generated file, a shared rule of the charter, a skill, hook or status line of a kiln plugin, a reusable workflow, the kiln or charter command) to https://github.com/antoine-tena/kiln - a pull request when the fix is clear and local, an issue otherwise, posted only with the user's consent. Use when a problem turns out to come from kiln rather than from this repo (rule [REPORT-TO-KILN]), or when the user asks to report something to kiln.Votes: 0GitHub stars: 2
- ReviewReview a branch's commits and diff before they become public for good - messages, authorship, forbidden trailers, stray files, secrets, fixups to fold - and tidy the history while it can still be rewritten; with `--repo`, review the whole repo before a release (published commits since the last tag, leftover remote branches, worktrees). Run by /kiln:merge before merging and by /kiln:release before tagging; use also when the user asks whether a branch or the repo is clean, presentable, ready to...Votes: 0GitHub stars: 2
- TokenSet up the credentials of a service (PyPI, Stripe, an API, a host…) in a `.<service>/` folder at the repo root - `token` (the raw secret, chmod 600) and `config` (key=value, comments on the token's scope) - and give the user the one command that pastes the token without showing it. Use when a task needs an API key or a token, or when the user wants to give one.Votes: 0GitHub stars: 2
- UpdateUpdate kiln - the kiln tool of the machine and its plugins, then the open repo (kiln update, on a branch merged right away into develop). Use when the user asks to update kiln, or accepts the update offered at session start.Votes: 0GitHub stars: 2
- WorktreeCreate a work branch in a ready-to-use git worktree. The normal way to start a branch, so as not to cross another session in the main tree.Votes: 0GitHub stars: 2
- NuxtNuxt full-stack Vue framework with SSR, auto-imports, and file-based routing. Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering.Votes: 0GitHub stars: 2
- PolishVisual audit of a page of the site with screenshots (desktop and mobile), a list of finish defects, then fixes. To make a page worthy of a high-end site.Votes: 0GitHub stars: 2
- PreviewSee a page or a dialog of the frontend as users do - a screenshot on three phones (iPhone 16, Galaxy A55, Galaxy S24) and a computer (1920 × 1080), logged in or not, then look at them. Use to check a rendering (new page, dialog, visual touch-up, overflow on mobile) or when the user asks to "see" something on mobile and desktop.Votes: 0GitHub stars: 2
- VitestVitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.Votes: 0GitHub stars: 2
- Vue Best PracticesMUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.Votes: 0GitHub stars: 2
- Vue Testing Best PracticesUse for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.Votes: 0GitHub stars: 2
- DeployDeploy the project to production with the repo's scripts (scripts/ops/), after checking that CI on the integration branch is green.Votes: 0GitHub stars: 2
- Prod DumpRestore a copy of the production database into a throwaway local PostgreSQL, to test a migration, a query or a script on real data without touching production.Votes: 0GitHub stars: 2
- Prod LogsDiagnose production on the VPS - container state, targeted logs, API health, system. Read-only. Use when the site or the API misbehaves.Votes: 0GitHub stars: 2