all publishers

RediSearch

@redisearch source repo

36 published skills

  1. ▌
    Lint · redisearch
    Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
    6.2k repo stars
  2. ▌
    Verify · redisearch
    Run full verification before committing or creating a PR. Use this when you want to create a PR.
    6.2k repo stars
  3. ▌
    Open Pr · redisearch
    Open a GitHub pull request for RediSearch. Use whenever you are asked to open a PR.
    6.2k repo stars
  4. ▌
    Close Pr · redisearch bundle
    Close or clean up a GitHub pull request for RediSearch. Use when asked to close a PR, choose between ordinary closure and cleanup closure, delete a PR branch, sanitize mistaken PR metadata, or clean up a mistaken or unwanted PR whose diff should not remain visible.
    6.2k repo stars
  5. ▌
    Code Review · redisearch
    Review C code changes for correctness, safety, and style. Use this when you want to review C code changes or PRs.
    6.2k repo stars
  6. ▌
    Pr Backport · redisearch
    Backport a merged PR to a release branch. Use this when you need to cherry-pick a fix or feature into an older branch.
    6.2k repo stars
  7. ▌
    Rust Review · redisearch
    Review Rust code changes for unsafe correctness, security and robustness, documentation quality, and C-to-Rust porting fidelity. Use this when you want to review Rust changes before merging.
    6.2k repo stars
  8. ▌
    Jj Workspace · redisearch
    Create or delete a jj (Jujutsu) workspace — a second checkout of this repo, sharing one repository. Use when you need to work on something side by side with the current checkout, for instance to leave a long build or test run undisturbed, and to clean the workspace up afterwards.
    6.2k repo stars
  9. ▌
    Port C Module · redisearch
    Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.
    6.2k repo stars
  10. ▌
    Run Rust Tests · redisearch
    Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
    6.2k repo stars
  11. ▌
    Add CI Platform · redisearch
    Add a new OS platform to RediSearch CI. Use when adding a new distro version, OS, or container target to the build/test matrix.
    6.2k repo stars
  12. ▌
    Docs Guidelines · redisearch
    General documentation guidelines that apply across all languages. Use this when writing or reviewing comments, docstrings, or doc headers in any code.
    6.2k repo stars
  13. ▌
    Jj Fix Conflicts · redisearch
    Fix merge conflicts in a jj change and its ancestors, starting from the oldest conflict. Use this when a jj change or its ancestors have conflicts that need resolving.
    6.2k repo stars
  14. ▌
    Review Rust Docs · redisearch
    Review the documentation of a Rust crate to ensure it meets our requirements and standards. Use this when you have done changes to Rust code.
    6.2k repo stars
  15. ▌
    Run C Unit Tests · redisearch
    Run C/C++ unit tests to verify correctness. Use this after making changes to C code to verify nothing is broken.
    6.2k repo stars
  16. ▌
    Run Python Tests · redisearch
    Run end-to-end Python tests after making changes to verify correctness. Use this when you want to verify your changes from an end-to-end perspective, after ensuring the build and Rust tests pass.
    6.2k repo stars
  17. ▌
    Write Flow Tests · redisearch
    Guidelines for writing Python flow tests (end-to-end behavioral tests). Use this when writing new Python tests in tests/pytests/, and as the review criteria when reviewing changes to them.
    6.2k repo stars
  18. ▌
    Write Rust Tests · redisearch
    Write Rust tests to verify correctness of Rust code. Use this when you want to write Rust tests.
    6.2k repo stars
  19. ▌
    Commit Guidelines · redisearch
    Dirty repo, uncommitted changes, commit, amend, split, changeset, PR history. Inspect repository state and prepare atomic Git commits or jj changesets. Use whenever the worktree is already dirty or you are about to commit or rewrite history.
    6.2k repo stars
  20. ▌
    Report Flaky Test · redisearch
    Report a flaky RediSearch test from a CI failure, Jira issue, test id, or local log. Use this to collect GitHub Actions logs/artifacts, find or create the right MOD Jira ticket, update existing flaky-test issues, and suggest immediate triage such as a trivial test-only fix or a temporary skip_until.
    6.2k repo stars
  21. ▌
    Adversarial Review · redisearch
    Commission an independent review of a change from an isolated reviewer, before opening or updating a PR or on demand by the user. For the agent requesting the review — if you were spawned to review something, you are the reviewer and this is not your skill.
    6.2k repo stars
  22. ▌
    Branch Out Release · redisearch bundle
    Create a new RediSearch public release branch from master or prepare branch-out changes. Use when branching a version line such as 8.10 from master, setting initial version.h, copying GitHub branch protection, adapting release-branch CI gates, triggering validation, or documenting follow-up master-to-release sync policy.
    6.2k repo stars
  23. ▌
    Jj Split Changeset · redisearch
    Split a jj (Jujutsu) changeset into smaller, focused changesets. Use when asked to break up a large changeset, split commits, reorganize changes across revisions, or create stacked PRs from a single changeset. Covers safe duplication-based workflows, file-path and hunk-level splitting without interactive commands.
    6.2k repo stars
  24. ▌
    Check Flow Coverage · redisearch
    Check which C source lines are not covered by Python flow tests. Use this when you want to ensure your C code changes are exercised by end-to-end Python tests. For Rust coverage, use /check-rust-coverage instead.
    6.2k repo stars
  25. ▌
    Check Rust Coverage · redisearch
    Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.
    6.2k repo stars
  26. ▌
    Run Rust Benchmarks · redisearch
    Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.
    6.2k repo stars
  27. ▌
    Run Macro Benchmarks · redisearch
    Run a RediSearch end-to-end macro benchmark from tests/benchmarks/*.yml via redisbench-admin. Use this when you want to measure whole-module performance (throughput/latency) against a real redis-server, not micro Rust or C++ benchmarks.
    6.2k repo stars
  28. ▌
    Rust Docs Guidelines · redisearch
    Guidelines for writing Rust documentation. Use this when you want to write Rust documentation.
    6.2k repo stars
  29. ▌
    Improve Flow Coverage · redisearch
    Improve Python flow test coverage for C source files. Runs /check-flow-coverage to find gaps, then writes or extends tests following /write-flow-tests guidelines.
    6.2k repo stars
  30. ▌
    Rust Tests Guidelines · redisearch
    Guidelines for writing Rust tests. Use this when you want to write Rust tests.
    6.2k repo stars
  31. ▌
    Bisect Perf Regression · redisearch
    Systematically bisect an end-to-end performance regression between two refs (tags/branches/commits) down to the exact offending commit(s). Use this when CI/customer benchmarks show one version is measurably slower than another and you need to attribute the cost to specific PRs.
    6.2k repo stars
  32. ▌
    Investigate Flaky Test · redisearch
    Investigate a RediSearch flaky-test report from a Jira key, CI failure, test id, or local logs. Use this to collect evidence, identify a supported root cause, and propose a real fix; if the evidence is insufficient, say so and ask for the missing data instead of suggesting workaround-only fixes or skip_until.
    6.2k repo stars
  33. ▌
    Read Unmodified C Module · redisearch
    Read the source of the C module we are working on, before we made any changes.
    6.2k repo stars
  34. ▌
    Analyze Rust Ffi Crate Surface · redisearch
    Determine which parts of the C codebase use Rust-defined C symbols. Use this when you want to understand which C code files may be impacted by changes to a Rust FFI crate.
    6.2k repo stars
  35. ▌
    Minimize Rust Ffi Crate Surface · redisearch
    Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests. Use this when you are refactoring a Rust FFI crate and want to remove unused symbols.
    6.2k repo stars
  36. ▌
    Rqe Iterator Suspend Resume · redisearch
    Implementation & review guide for suspend/resume (revalidation) on query-engine iterators in src/redisearch_rs/rqe_iterators/. Use this when adding the Box<Self> suspend/resume mechanism to an RQE iterator that currently only implements the legacy revalidate, when modifying an existing suspend/resume implementation, or when reviewing a PR that touches this machinery (boxed.rs, ref_mode markers, child-slot helpers, layout-invariant proofs).
    6.2k repo stars