A plugin for RuboCop code style enforcing & linting tool. It includes Rubocop configuration used at Airbnb and a few custom rules that have cause internal issues at Airbnb but are not supported by core Rubocop.
This gem provides linters for detecting common 'smells' in `.feature` files. In addition to the provided linters, custom linters can be made in order to create custom linting rules.
Shared scss-lint rules for SASS projects in GOV.UK
Rules for linting code at Panorama Education
Validates RAML file (and JSON schema), runs a configurable set of linting rules, and produces HTML documentation.
Lookout-Rack Lookout-Rack provides easy interaction with Rack¹ from Lookout². It provides you with a session connected to your Rack application through which you can make requests, check responses, follow redirects and set, inspect, and clear cookies. ¹ See http://rack.rubyforge.org/ ² See http://disu.se/software/lookout/ § Installation Install Lookout-Rack with % gem install lookout-rack § Usage Include the following code in your ‹Rakefile› (provided that you’re using Lookout-Rake¹): require 'lookout-rack-3.0' Lookout::Rake::Tasks::Test.new do |t| t.requires << 'lookout-rack-3.0' end ¹ See http://disu.se/software/lookout-rake/ Then set up a ‹fixtures/config.ru› file that Lookout-Rack will use for loading your Rack app. load 'path/to/app.rb' use Rack::Lint run Path::To::App This file, if it exists, will be loaded during the first call to #session. If it doesn’t exist, ‹config.ru› will be used instead. You can now test your app: Expectations do expect 200 do session.get('/').response.status end end The #session method returns an object that lets you #get, #post, #put, and #delete resources from the Rack app. You call these method with a URI¹ that you want to access/modify together with any parameters that you want to pass and any Rack environment that you want to use (which isn’t very common). For example, let’s get ‹/pizzas/› with olives on them: expect 200 do session.get('/pizzas/', 'olives' => '1').response.status end ¹ Abbreviation for Uniform Resource Identifier The #response method on #session returns a mock Rack response object that can be queried for results. Similarly, there’s a #request method that lets you inspect the request that was made. Lookout-Rack also deals with cookies. Assuming that ‹/cookies/set/› will set any cookies that we pass it and that ‹/cookies/show/› will simply do nothing relevant, the following expectation will pass: expect 'value' => '1' do session. get('/cookies/set/', 'value' => '1'). get('/cookies/show/').request.cookies end Sometimes you may want to set cookies yourself before making a request. You then use the #cookie method, which takes a String of ‹KEY=VALUE› pairs separated by newlines, commas, and/or semicolons and sets those cookies in the session: expect 'value' => '1', 'other' => '2' do session. cookie("value=1\n\nother=2"). get('/cookies/show/').request.cookies end You may also want to clear all cookies in your session using #clear: expect({}) do session. get('/cookies/set', 'value' => '1'). clear. get('/cookies/show').request.cookies end Finally, to test redirects, call the #redirect! method on the session object, assuming that ‹/redirected/› redirects to another location: expect result.redirect? do session.get('/redirected/').response end expect result.not.redirect? do session.get('/redirected/').redirect!.response end That’s basically all there’s to it. You can check the {API documentation}¹ for more information. ¹ See http://disu.se/software/lookout-rack/api/Lookout/Rack/ § Financing Currently, most of my time is spent at my day job and in my rather busy private life. Please motivate me to spend time on this piece of software by donating some of your money to this project. Yeah, I realize that requesting money to develop software is a bit, well, capitalistic of me. But please realize that I live in a capitalistic society and I need money to have other people give me the things that I need to continue living under the rules of said society. So, if you feel that this piece of software has helped you out enough to warrant a reward, please PayPal a donation to now@disu.se¹. Thanks! Your support won’t go unnoticed! ¹ Send a donation: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=now@disu.se&item_name=Lookout-Rack § Reporting Bugs Please report any bugs that you encounter to the {issue tracker}¹. ¹ See https://github.com/now/lookout-rack/issues § Authors Nikolai Weibull wrote the code, the tests, the documentation, and this README. § Licensing Lookout-Rack is free software: you may redistribute it and/or modify it under the terms of the {GNU Lesser General Public License, version 3}¹ or later², as published by the {Free Software Foundation}³. ¹ See http://disu.se/licenses/lgpl-3.0/ ² See http://gnu.org/licenses/ ³ See http://fsf.org/
Rules for linting Ruby code at Panorama Education. Use the latest git commit of this gem instead of the version pushed to RubyGems.
A plugin for RuboCop code style enforcing & linting tool. It includes Rubocop configuration used at Church of the Highlands and a few custom rules that have caused internal issues at Church of the Highlands but are not supported by core Rubocop.
Rules for linting Rails code at Panorama Education. Use the latest git commit of this gem instead of the version pushed to RubyGems.
Lints Markdown prose and code comments with pattern and counting rules.
Ask an AI coding agent to move a button 10 pixels left, and watch it struggle. CSS gives it five or six different ways to control position: margin, padding, a flex order, a grid column, a transform. Nothing says which one is actually in charge on this particular page, so the agent guesses, edits the wrong one, and something else quietly shifts. It reports the change as done. The page is now broken. QSS removes the guessing by removing the choice. Every element's position and size is one explicit number, not a tug-of-war between properties. Those numbers are written in a single unit, a "qnt" (1/1000th of the layout's own width), so the same edit holds its exact proportion at any screen size -- a phone, a laptop, a 4K display -- with no breakpoints, no media queries, and no separate rules to keep in sync. Move something once and it stays put, everywhere. That is the whole idea, and it helps humans exactly as much as it helps agents: fewer rules to maintain, one obvious place to make a change, and layouts that stay consistent across devices by construction instead of by discipline. QSS backs that up with two automatic auditors that catch mistakes a human reviewer might miss (a RED finding is a broken rule, ORANGE is a judgment call) and a real-browser render check, because a passing lint rule is not proof a page actually displays correctly -- only watching it render is. It ships compiled, ready-to-use CSS plus its SCSS source, works with zero JavaScript, and offers an optional JS engine for a few conveniences on top. It stays out of the way of whatever you use for colors, type and visual polish (Tailwind or anything else) -- QSS only ever owns position, size and structure. QSS was extracted from a real Rails development tool that still runs on it today, not built as a theoretical exercise. See docs/HOWTO.md to get started and docs/DESIGN_HISTORY.md for the full story of what was tried, what broke, and why each decision landed where it did. Status: 0.x. Expect names and APIs to change before 1.0.
Lintus reads linting rules from a YAML file at the root of your repository, asks the Typesafe Jev model each rule as a noul question against every matching file, and reports an offense wherever the model says so. Runs on a whole tree, a git diff, or the staged files of a commit.
Constable replaces RSpec/Minitest for Rails apps that want tests to be fast and non-flaky by construction. Every test is isolated by default, nondeterminism is a lint error rather than a CI surprise, and every escape hatch is reported until someone deals with it. Existing RSpec and Minitest suites adopt it with a one-line change per file and zero rewriting -- cold cases run verbatim through their original engine while native cases run under strict rules, side by side in one run. Ships with a case-file DSL (investigate/witness/briefing/docket), transactional isolation, flake history with rename-surviving content-hash identity, a jail and parole docket for legacy red suites, warrants for automatic flake detection, diff-based coverage, parallel workers, git-diff test selection, and a RuboCop extension. The gem is published as "constable-rails"; everything inside it -- the module, the CLI, the config directory -- is simply "constable".
Lumin provides configurable lint rules, parallel execution, caching, and safe autocorrection.
Rubyzen is a modern linter for Ruby that allows you to write architectural lint rules as unit tests. In the era of AI-generated code, it provides your team with deterministic guardrails to keep your codebase clean, maintainable, and consistent as it grows.
A configurable lint engine for SAS source files. Walks the token stream produced by the `sas-lexer` gem and applies a set of pluggable rules covering structural defects (malformed `if` conditions, identical `then`/`else` branches, unreachable inner branches), cosmetic issues (trailing whitespace, tab expansion, line endings, encoding gremlins), and source-header conventions. Includes a `bin/sas_lint` CLI and YAML-based config.
Mdlint is a Pure Ruby Markdown linter and formatter with no external dependencies. It provides configurable lint rules and automatic formatting for consistent Markdown files.
Ikuzo delivers short, humorous, and motivational commit messages so you can satisfy Conventional Commit lint rules and get back to coding—life is short, take time to code—whether you call it from the CLI or as a library.
The standard Rubocop rules for the DVLA