Command line tool for applying GitHub Pull Requests
Auto-apply PR reviews with Claude Code
Helper functions around Function call/apply/bind, for use in `call-bind`
Push an array of items into an array, while being robust against prototype modification
Apply GitHub Pull Requests
Takes a release plan and applies it to packages
Apply a diff to an object. Optionally supports jsonPatch protocol
Add components to your apps.
Workflow runtime for AI agents - deterministic pipelines with approval gates
Expensify libraries and components shared across different repos
An iterative AI task execution framework. Orchestrates multi-phase autonomous work using Claude or Codex engines.
[](https://www.npmjs.com/package/@smithy/middleware-apply-body-checksum) [![NPM downloads](https://img.shields.io/npm/dm/@smithy/middleware-apply-body-checksum.s
Various method to process spectra
Allow outside contributors to indicate what semver label should be applied to the Pull Request
Take an array of string index ranges, delete/replace the string according to them
Autonomous PR CI monitor and review-comment resolver for agentic coding tools
UnoCSS transformer for `@apply` directive
Webpack loader that adjusts source maps
Apply ES2015 function.name semantics to all functions
Utilities for validating and updating "Keep a Changelog" formatted changelogs
Apply a source map to a vinyl file, merging it with preexisting source maps
PostCSS plugin enabling custom properties sets references
kody — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.
Parse a JSON string that has git merge conflicts, resolving if possible
NOTE: This is a temporary gem. It is a workaround for rodjek/librarian-puppet PR #328. Simplify deployment of your Puppet infrastructure by automatically pulling in modules from the forge and git repositories with a single command.
A CLI wrapper around `rails new` that applies preset flags (-d postgresql -T --api --minimal), adds a curated set of gems (RSpec, RuboCop, factory_bot, Bullet, SimpleCov, test-prof), and bootstraps Claude Code slash commands for common development tasks (fix, lint, commit, review-pr, add-tests, code-coverage, docs, deliver).
# XQuery [](https://gitter.im/JelF/xquery?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [](https://travis-ci.org/JelF/xquery) [](https://codeclimate.com/github/JelF/xquery) [](https://codeclimate.com/github/JelF/xquery/coverage) [](https://codeclimate.com/github/JelF/xquery) XQuery is designed to replace boring method call chains and allow to easier convert it in a builder classes ## Usage of `XQuery` function `XQuery` is a shortcat to `XQuery::Generic.with` ``` r = XQuery(''.html_safe) do |q| # similar to tap q << 'bla bla bla' q << 'bla bla bla' # using truncate q.truncate(15) # real content (q.send(:query)) mutated q << '!' end r # => "bla bla blab...!" ``` ## Usage of `XQuery::Abstract` I designed this gem to help me with `ActiveRecord` Queries, so i inherited `XQuery::Abstract` and used it's powers. It provides the following features ### `wrap_method` and `wrap_methods` when you call each of this methods they became automatically wrapped (`XQuery::Abstract` basically wraps all methods query `#respond_to?`) It means, that there are instance methods with same name defined and will change a `#query` to their call result. ``` self.query = query.foo(x) # is basically the same as foo(x) # when `wrap_method :foo` called ``` You can also specify new name using `wrap_method :foo, as: :bar` syntax ### `q` object `q` is a proxy object which holds all of wrapped methods, but not methods you defined inside your class. E.g. i have defined `wrap_method(:foo)`, but also delegated `#foo` to some another object. If i call `q.foo`, i will get wrapped method. Note, that if you redefine `#__foo` method, q.foo will call it instead of normal work. You can add additional methods to `q` using something like `alias_on_q :foo`. I used it with `kaminary` and it was useful ``` def page=(x) apply { |query| query.page(x) } end alias_on_q :page= def page query.current_page end alias_on_q :page ``` ### `query_superclass` You should specify `query_superclass` class_attribute to inherit `XQuery::Abstract`. Whenever `query.is_a?(query_superclass)` evaluate to false, you will get `XQuery::QuerySuperclassChanged` exception. It can save you much time when your class misconfigured. E.g. you are using `select!` and it returns `nil`, because why not? ### `#apply` method `#apply` does exact what it source tells ``` # yields query inside block # @param block [#to_proc] # @return [XQuery::Abstract] self def apply(&block) self.query = block.call(query) self end ``` It is usefull to merge different queries. ### `with` class method You can get XQuery functionality even you have not defined a specific class (You are still have to inherit XQuery::Abstract to use it) You can see it in this document when i described `XQuery` function. Note, that it yields a class instance, not `q` object. It accepts any arguments, they will be passed to a constructor (except block) ### `execute` method Preferred way to call public instance methods. Resulting query would be returned
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.