All authors
Claude Skills by Dimkox
github.com/Dimkox16 skills0 installs0 views
- Ai Rag ChangeUse for LLM, RAG, vector search, embeddings, prompts, agent tools, evaluations, or AI-assisted product behavior.Votes: 0GitHub stars: 2
- Api Event ChangeUse when changing REST/HTTP APIs, webhooks, events, queues, schemas, producers, consumers, or event-driven workflows.Votes: 0GitHub stars: 2
- Bitrix DevelopmentUse for any 1C-Bitrix or Bitrix24 repository task involving modules, components, events, agents, ORM, CRM, REST, cache, permissions, or legacy APIs.Votes: 0GitHub stars: 2
- Bugfix WorkflowUse for defects, regressions, exceptions, and hotfixes. Requires reproduction, root-cause evidence, a failing regression test, minimal repair, and verification.Votes: 0GitHub stars: 2
- Data ChangeUse for SQL schema changes, migrations, indexes, backfills, Elasticsearch/OpenSearch mappings, ClickHouse pipelines, and data-quality work.Votes: 0GitHub stars: 2
- Enterprise IntegrationUse for 1C, Bitrix24, SAP, ERP, WMS, BI, payment, CRM, or other external-system adapters and synchronization.Votes: 0GitHub stars: 2
- Feature WorkflowUse for new behavior, new subsystems, and architectural changes. Converts outcomes into acceptance criteria, bounded design, vertical tasks, tests, rollout, and rollback.Votes: 0GitHub stars: 2
- Frontend ChangeUse for browser UI, JavaScript/TypeScript, React/Vue, CSS, accessibility, or Cypress/Playwright flows.Votes: 0GitHub stars: 2
- Getzilla DeliveryUse for every routed software-development task. Reads the active route, dispatches only selected agents, enforces one write owner, and closes the task with fingerprint-bound verification and independent review evidence.Votes: 0GitHub stars: 2
- Incident ResponseUse for production outages, severe regressions, data incidents, or urgent hotfixes where containment and evidence preservation precede repair.Votes: 0GitHub stars: 2
- Legacy ModernizationUse for refactoring or replacing legacy code while preserving behavior and controlling architecture debt.Votes: 0GitHub stars: 2
- Release ReadinessUse for release, deployment, migration rollout, canary, rollback, or final go/no-go preparation.Votes: 0GitHub stars: 2
- Security Sensitive ChangeUse for authentication, authorization, permissions, secrets, PII, payment, production, tenant isolation, or irreversible actions.Votes: 0GitHub stars: 2
- Seo LandingGenerate, audit, or optimize fast static SEO landing pages with explicit evidence and safe mode boundaries. Use when a user requests an SEO-focused landing or one-pager, PageSpeed improvements, a read-only landing audit, or targeted fixes to an existing landing.Votes: 0GitHub stars: 2
- Task TriageUse when a request is ambiguous, research-oriented, or needs scope classification before design or code.Votes: 0GitHub stars: 2
- Verification EvidenceUse whenever tests, review, CI evidence, or completion claims must be checked and bound to the current repository state.Votes: 0GitHub stars: 2