All authors
Claude Skills by tmj-90
github.com/tmj-90124 skills1 installs67 views
- Python ConventionsUse when a ticket adds or changes Python code and it must follow the repo's Python conventions — PEP 8, full type hints (PEP 484) checked by mypy/pyright, dataclasses, pythonic idioms, explicit error handling, asyncio and thread safety, ruff-clean, and pytest with coverage via the repo's env manager (uv/poetry). Invoke for "add this in Python", "fix the type/lint errors", "add the FastAPI/Django endpoint", or as the language pack for any Python change or Python review.Votes: 0GitHub stars: 2
- Record EvidenceUse after implementing a Dispatch ticket and running its checks, to produce and record acceptance-criterion evidence, then STOP. Invoke whenever you have finished and committed work on your claimed ticket and need to evidence each AC. Recording evidence is where your job ENDS — the runner (not you) records the delivery, submits for review, and pushes/opens the PR when PR creation is enabled.Votes: 0GitHub stars: 2
- Refactor ModuleUse when a ticket asks to restructure code without changing what it does — extract a function, split a file, rename for clarity, reduce duplication — with behaviour preserved. Invoke for "refactor X", "clean up the Y module", or "extract Z" where no behaviour change is intended.Votes: 0GitHub stars: 2
- Resolve Merge ConflictUse when an approved ticket's delivery branch cannot auto-merge into the default branch because of a merge conflict. Invoke for "resolve the merge conflict on branch X", "the auto-merge conflicted — reconcile it", or when the factory's merge-ticket runner hands you a conflicting gaffer/* branch. Merge the default branch INTO the delivery branch, resolve every conflict by preserving BOTH intents, prove it with tests, and commit the resolution ON THE BRANCH — never land it to the default branch...Votes: 0GitHub stars: 2
- Review TicketUse as a reviewer agent to review another agent's `in_review` ticket — never your own. Judge whether each acceptance criterion is genuinely met and proven by a test that exercises that criterion's own behaviour, and whether the change is sound, then record an ADVISORY verdict (per-AC evidence + an overall RECOMMEND APPROVE / RECOMMEND CHANGES line) via the scoped Dispatch MCP, leaving the ticket `in_review` for a HUMAN to make the final approve/reject decision. An agent review is NOT a human ...Votes: 0GitHub stars: 2
- RiceUse when prioritising a feature backlog using RICE scoring (Reach, Impact, Confidence, Effort) or making a capacity-constrained prioritisation decision. Triggers on "prioritise these features", "RICE scoring", "what should we build first", "rank the backlog", or "capacity planning for the sprint".Votes: 0GitHub stars: 2
- Run CoverageUse when a ticket or acceptance criterion sets a coverage threshold or asks to raise coverage on a unit, and you need to measure it, find the uncovered branches, and evidence the number. Invoke for "coverage must stay above N%", "cover the new module", "which paths are untested", or a mutation-score check on changed code.Votes: 0GitHub stars: 2
- Run LintUse when a ticket or acceptance criterion requires the linter/formatter to pass, or after editing code to confirm it meets the repo's style and static-analysis rules before submitting for review. Invoke for "lint must pass", "fix the formatting", "no new warnings", or as the last check before you self-review.Votes: 0GitHub stars: 2
- Run TestsUse when a ticket or acceptance criterion needs the test suite run and its result evidenced, or after making a change to confirm nothing broke. Invoke for "tests must pass", "verify the suite is green", or before handing any code change to review — and to check that each acceptance criterion has a test that exercises it.Votes: 0GitHub stars: 2
- Runbook GeneratorUse when a service has no runbook, existing runbooks are inconsistent across teams, or on-call onboarding requires standardised operations docs. Triggers on "write a runbook", "document on-call procedures", "operational playbook", "incident playbook", or "runbook for <service>".Votes: 0GitHub stars: 2
- Schema MarkupUse when implementing, auditing, or validating structured data (schema markup) on a website. Triggers on "structured data", "schema.org", "JSON-LD", "rich results", "rich snippets", "FAQ schema", "Product schema", "schema errors in Search Console", or "why no rich results". NOT for general SEO audits — use `seo-audit`. For AI-search citation optimisation, use `aeo`.Votes: 0GitHub stars: 2
- Security AuthzUse when a ticket touches authorization — who may perform an action or see a resource — adding access checks, roles/permissions, ownership/tenant scoping, or fixing an access-control gap. Invoke for "restrict X to admins", "add an ownership check", "enforce tenant isolation", or any change to protected resources.Votes: 0GitHub stars: 2
- Security Input ValidationUse when a ticket handles untrusted input — request bodies/params, query strings, headers, uploads, webhooks, or third-party API responses — and it must be validated and safely handled. Invoke for "validate the request", "sanitize user input", "fix the injection/XSS risk", or when adding any boundary that ingests external data.Votes: 0GitHub stars: 2
- Security Secret HandlingUse when a ticket involves secrets — API keys, tokens, passwords, connection strings, signing keys — or their configuration, storage, logging, or rotation. Invoke for "wire up the API key", "load config from the environment", "stop logging the token", or when adding any integration that needs a credential.Votes: 0GitHub stars: 2
- Self ReviewUse after implementing a ticket and after its tests pass, but before submitting for review, to review your own diff as a skeptic would. Checks the finished `git diff` against every acceptance criterion (is each genuinely satisfied, and proven by a test that exercises that criterion's own behaviour?), against scope (did you change only what the ticket needs?), and against quality (bugs, concurrency and failure paths, leftover debug, missed edge cases, repo conventions). If the diff reveals a g...Votes: 0GitHub stars: 2
- Seo AuditUse when auditing, reviewing, or diagnosing SEO issues on a site. Triggers on "SEO audit", "technical SEO", "why am I not ranking", "SEO issues", "on-page SEO", "meta tags review", or "SEO health check". For structured data specifically, use `schema-markup`. For AI-search citation optimisation, use `aeo`.Votes: 0GitHub stars: 2
- Slides DeckUse when asked to create a slide deck, presentation, pitch deck, or talk outline — or to convert a markdown document into a slides format (Marp, Slidev, reveal.js). Triggers on "create a deck", "slide deck", "presentation", "pitch deck", "talk slides", "convert to slides", or "markdown to slides".Votes: 0GitHub stars: 2
- Slo ArchitectUse when defining, reviewing, or operating SLOs and SLIs — error budgets, burn-rate alerting, SLO review gates. Triggers on "define an SLO", "error budget", "burn rate", "SLI", "multi-window burn-rate alert", or any reliability-target question. For broader dashboard/alert-noise work, route to `observability-designer`.Votes: 0GitHub stars: 2
- Spec AuthorUse to turn a brief into a structured product SPEC — a set of testable CLAUSES, each exactly one statement, tagged requirement / non-goal / decision — that a human edits and freezes before it feeds the decompose engine. Clarify genuine load-bearing ambiguity first, then draft, making the brief's quality requirements (persistence, concurrency, failure behaviour, runtime support, security) explicit testable clauses. Invoke whenever someone describes an app or feature and wants the intent captur...Votes: 0GitHub stars: 2
- Submit ReviewReference for how a finished ticket reaches human review in the Gaffer factory. Submission is RUNNER-OWNED — the agent commits its work and evidences the ACs, then stops; the runner records the delivery and submits for review (and pushes / opens a PR only when the operator enabled that). Invoke when you think your work is ready to hand off, to confirm what you must do (commit + evidence) and what the runner does for you (gates, submit, optional push/PR).Votes: 0GitHub stars: 2
- Terraform PatternsUse when designing Terraform modules, managing state backends, reviewing IaC for security or anti-patterns, implementing multi-region deployments, or standardising Terraform CI/CD. Triggers on ".tf files", "Terraform module", "remote state", "IaC review", "Terraform security", or "multi-region infra".Votes: 0GitHub stars: 2
- Threat DetectionUse for threat hunting and detection-as-code — Sigma or SIEM detection rules (one tested rule per technique), a sweep of IOCs, behavioural anomalies in telemetry, and each hypothesis hunt mapped to MITRE ATT&CK techniques.Votes: 0GitHub stars: 2
- Typescript ConventionsUse when a ticket adds or changes TypeScript/JavaScript code and it must follow the repo's TS conventions — strict mode typing, typescript-eslint type-aware rules, async correctness (no floating promises, bounded fan-out), boundary validation instead of casts, module/import hygiene, Node resource and concurrency safety, and idiomatic patterns. Invoke for "add this in TypeScript", "fix the type errors", "tighten the types on X", or as the language pack for any TS/JS change or TS/JS review.Votes: 0GitHub stars: 2
- Update DocsUse when a ticket requires documentation to reflect a change — a README, API reference, changelog, or runbook — or when an acceptance criterion says "document X". Invoke for "update the docs for the new endpoint", "add a changelog entry", or "the README is now wrong".Votes: 0GitHub stars: 2
- User StoryUse when generating user stories with acceptance criteria, or planning sprint capacity against a set of stories. Triggers on "write user stories", "create stories for this feature", "break this into stories", "sprint planning", or "story points".Votes: 0GitHub stars: 2
- Accessibility ReviewUse as a REVIEW LENS when judging another agent's UI diff for accessibility defects against WCAG 2.2 AA — missing labels and names, keyboard traps or unreachable controls, focus not managed or obscured, colour-only meaning, insufficient contrast, small targets, drag-only interactions, unannounced dynamic changes — before recommending approval. Invoke on every review of a ticket that adds or changes user interface; it complements review-ticket and frontend-a11y (the builder's skill), it does n...Votes: 0GitHub stars: 2
- Add Cli CommandUse when a ticket adds or changes a command-line interface — a new subcommand, flag, or output format for the repo's CLI tool — and it must follow the CLI's existing conventions for arguments, exit codes, JSON output, help text, and tests. Invoke for "add a `foo bar` command", "add a --json flag", "the CLI should print X", or any change under a cli/ or bin/ entry point.Votes: 0GitHub stars: 2
- Add Config OptionUse when a ticket adds or changes a configuration option — an environment variable, a settings key, a CLI flag, a YAML field — that operators set, and it must have one source of truth, a validated default, precedence rules, and documentation that cannot drift. Invoke for "make X configurable", "add an env var for Y", "expose a setting", or "the default should be Z".Votes: 0GitHub stars: 2
- Add Feature FlagUse when a ticket asks to ship behaviour behind a toggle — a gradual rollout, a kill switch, an A/B variant, a dark launch — or to add, wire, or clean up a feature flag with a default, an owner, and a removal plan. Invoke for "put it behind a flag", "add a kill switch", "roll out to 10%", or "remove the flag now that it's fully on".Votes: 0GitHub stars: 2
- Api VersioningUse when a ticket must change an API in a way clients might notice — renaming or removing a field, changing a type or status code, altering semantics — and the change must be made compatibly or through an explicit version with a deprecation path, never as a silent break. Invoke for "change the response shape", "rename the field", "we need v2", "deprecate the old endpoint", or when a contract test fails on purpose.Votes: 0GitHub stars: 2
- Auth Session And OauthUse when a ticket touches how a user proves who they are — login, logout, sessions, cookies, JWTs, refresh tokens, password reset, OAuth/OIDC sign-in with a provider, API keys — and the implementation must use the repo's existing auth library and the platform's primitives correctly, never home-grown crypto. Invoke for "add login with Google", "sessions expire too fast", "implement password reset", "rotate the API key", or any authentication change.Votes: 0GitHub stars: 2
- Background JobsUse when a ticket moves work off the request path or adds asynchronous processing — a job queue, a worker, an outbox, "send the email later", "process uploads in the background", retries for a failed job — and the job must be idempotent, observable, bounded, and safe to run twice. Invoke for any queue, worker, or deferred-processing change.Votes: 0GitHub stars: 2
- Caching StrategyUse when a ticket adds, changes, or debugs a cache — an in-memory memo, an HTTP cache header, a Redis layer, a CDN rule, a query-result cache — and the change must state what is cached, for how long, what invalidates it, and what happens when it is wrong. Invoke for "cache this", "it's showing stale data", "add Cache-Control", or when a profile shows the same read repeated.Votes: 0GitHub stars: 2
- Concurrency And AsyncUse when a ticket involves work happening at the same time — async/await flows, promises and futures, goroutines and channels, threads and locks, parallel requests, races, deadlocks, "sometimes it double-processes" — and the change must be correct under interleaving, not just on the happy sequence. Invoke for any concurrency bug, any new parallelism, any shared mutable state, or any code where two requests, workers or processes can write the same file, row, counter or lock.Votes: 0GitHub stars: 2
- Contract TestUse when a ticket changes the boundary between two components or services — an HTTP API and its client, a message producer and consumer, a public module interface — and both sides must keep agreeing. Invoke for "don't break the client", "add a contract test", a consumer-driven contract (Pact), schema validation against OpenAPI/JSON Schema/protobuf, or whenever a change touches a schema another team or repo depends on.Votes: 0GitHub stars: 2
- Csharp ConventionsUse when a ticket adds or changes C#/.NET code — ASP.NET Core services, libraries, workers — and it must follow the repo's C# conventions — the .NET coding conventions, nullable reference types on and honoured, async all the way with cancellation tokens, dependency injection through the container with correct lifetimes, records for values, IDisposable and thread safety handled, Roslyn analyzers and dotnet format clean — as the language pack for any C# change. Invoke for "add this in C#", "fix...Votes: 0GitHub stars: 2
- Data PrivacyUse when a ticket handles personal data — collecting a new field about a person, exporting or deleting a user's data, retention and anonymisation, analytics events, sharing with a third party — and the change must minimise what is collected, protect it in storage and logs, honour deletion and access requests, and be explainable to a regulator. Invoke for GDPR/CCPA-style work, "add a tracking event", "delete my account", "export user data", or any new column that describes a person.Votes: 0GitHub stars: 2
- Debug Failing CiUse when a ticket is about a red pipeline — a job that fails in CI but passes locally, a build that broke on the default branch, a flaky or slow workflow — and the fix must be the real cause, not a retry or a skipped step. Invoke for "CI is red", "works on my machine", "the deploy job fails", or before touching a workflow file to make a check pass.Votes: 0GitHub stars: 2
- Dependency UpgradeUse when a ticket bumps, adds, or removes a dependency — a security advisory, a major-version upgrade, a lockfile refresh, a Dependabot follow-up — and the change must be proven safe with the repo's tests and the upstream changelog, not assumed. Invoke for "upgrade X to v4", "fix the audit finding", "remove the unused package", or any change to a manifest or lockfile.Votes: 0GitHub stars: 2
- Deprecate And RemoveUse when a ticket retires something — a feature flag, an endpoint, a config option, a module, a column, a CLI command — and the removal must not break callers, data, or operators who still depend on it. Invoke for "remove the legacy X", "delete dead code", "drop the old API", or "clean up after the migration".Votes: 0GitHub stars: 2
- E2e Browser TestUse when a ticket asks for end-to-end or browser coverage of a user journey — sign-up, checkout, a form submission, a dashboard flow — driven through the real UI with Playwright, Cypress, or the repo's browser harness. Invoke for "add an e2e test", "cover the flow in the browser", or when an acceptance criterion can only be shown by clicking through the app.Votes: 0GitHub stars: 2
- Error HandlingUse when a ticket touches how failures are represented, propagated, or reported — a new error type, a retry, a fallback, "handle the case where X fails", swallowed exceptions, or unclear error messages — and the result must fail loudly where it should and recover only where it can. Invoke for "handle errors properly", "don't crash on X", or when a reviewer flags an empty catch.Votes: 0GitHub stars: 2
- Event Driven MessagingUse when a ticket connects components through events or messages — publishing domain events, consuming from a topic or stream, an event bus, pub/sub, change-data-capture — and the design must define ownership of each event, its schema and versioning, delivery guarantees, ordering, and how consumers stay idempotent. Invoke for "emit an event when X", "subscribe to Y", "add a consumer", "events are arriving out of order", or any Kafka/SNS/SQS/NATS/Redis Streams work.Votes: 0GitHub stars: 2
- File UploadsUse when a ticket lets users send files — avatars, documents, CSV imports, attachments — or serves them back, and the path must be safe against oversized, malicious, or mis-typed content, store files outside the web root or in object storage, and never trust the client's filename or content type. Invoke for "let users upload X", "add an import", "serve the attachment", or any multipart or presigned-URL work.Votes: 0GitHub stars: 2
- Fix BugUse when a ticket reports defective behaviour — a wrong result, a crash, a regression, "X doesn't work when Y" — and the fix must be proven with a test that fails before and passes after. Invoke for any bug, incident follow-up, or "this used to work" ticket before touching the code.Votes: 0GitHub stars: 2
- Frontend Data FetchingUse when a ticket loads or mutates server data from the client — fetching a list or a detail, polling, live updates, mutations with cache updates or optimistic UI, loading and error states, retries, concurrent edits — and the implementation must use the repo's data layer, never fetch in a bare effect, and handle loading, empty, error, stale and offline states visibly. Invoke for "load the X from the API", "it flashes empty then loads", "the list doesn't refresh after saving", or "add live upd...Votes: 0GitHub stars: 2
- Frontend Forms And ValidationUse when a ticket builds or changes a form — inputs, validation, error display, submission, multi-step flows, file fields — and it must validate with the same schema the server uses, be fully keyboard- and screen-reader-usable, and handle every state (pristine, invalid, submitting, failed, succeeded) without losing the user's work or submitting twice. Invoke for "add a form for X", "validation is inconsistent", "the error isn't shown", or "the form clears on error".Votes: 0GitHub stars: 2
- Frontend PerformanceUse when a ticket is about a slow or heavy frontend — page load, bundle size, Core Web Vitals (LCP, INP, CLS), a janky list, re-render storms, large images or fonts — and the fix must be measured in the browser before and after with the same tooling, not guessed. Invoke for "the page is slow", "reduce the bundle", "fix the layout shift", "the table lags when typing", or a failing performance budget.Votes: 0GitHub stars: 2
- Frontend State ManagementUse when a ticket adds or reshapes client-side state — where data lives, how it flows between components, server cache versus UI state, a store, context, URL state, persisted drafts, optimistic updates, multiple tabs — and the result must keep one source of truth per fact and avoid the prop-drilling or global-store sprawl that makes UIs unpredictable. Invoke for "the state is out of sync", "lift this state", "add a store for X", or "the page resets when I navigate back".Votes: 0GitHub stars: 2
- Frontend TestingUse when a ticket needs tests for UI code — a component's behaviour, a hook, a form, a page's states, accessibility assertions, visual regressions — below the full browser end-to-end level, using the repo's component test runner and testing-library conventions. Invoke for "add tests for the component", "cover the hook", "test the empty and error states", or when a frontend change ships without tests.Votes: 0GitHub stars: 2