# lint

Lint is a static analysis tool or program that examines source code to detect bugs, inefficiencies, irregularities, and non-portable constructs.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Native lint and typecheck Deployment Checks are being deprecated

DevFeed: [Native lint and typecheck Deployment Checks are being deprecated](<https://devfeed.tech/articles/native-lint-and-typecheck-deployment-checks-are-being-deprecated-138698.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/native-lint-and-typecheck-deployment-checks-are-being-deprecated>)

Author: Cody Wong

Published: 2026-11-17T13:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ci](<https://devfeed.tech/tags/ci.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [lint](<https://devfeed.tech/tags/lint.md>), [native](<https://devfeed.tech/tags/native.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel is removing its native lint and typecheck Deployment Checks on November 30, 2026; new checks can no longer be added. Existing checks run in parallel with deployment builds. Move their commands to Vercel CI or another CI workflow before removal, and check failure handling if they block production releases. Running them in the Build Command is another option, but may increase build time and any error will fail the deployment build. Other Deployment Checks and commands already running in GitHub Actions or the Build Command are unaffected.

### Source excerpt

Native lint and typecheck Deployment Checks are being deprecated. Use Vercel CI or your own CI workflows to continue running these tasks. What this means These checks run your repository's lint and typecheck tasks on Vercel in parallel with deployment builds. New checks can no longer be added. Existing checks continue running until November 30, 2026, when they're removed. Other Deployment Checks and commands already running in GitHub Actions or your Build Command are unaffected. How to migrate Affected checks appear as Lint or Typecheck entries with Vercel as the provider in your project's Build and Deployment settings. Move their commands before removal. For checks that block production releases, verify how the new workflow handles failures. You can also run these commands in your Build Command, though that may increase build time and an error will fail the deployment build. Try this prompt to ask your coding agent to help migrate your lint and typecheck tasks to Vercel CI: Read the Vercel CI documentation to learn more. Read more

## ReSharper C++ 2026.3: Class Layout, Format String Analysis, And More

DevFeed: [ReSharper C++ 2026.3: Class Layout, Format String Analysis, And More](<https://devfeed.tech/articles/resharper-c-2026-3-class-layout-format-string-analysis-and-more-127491.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/rscpp/2026/11/10/resharper-cpp-2026-3-class-layout-format-string-analysis-and-more/>)

Author: Igor Akhmetov

Published: 2026-11-10T16:37:04Z

Content type: release

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [resharper](<https://devfeed.tech/topics/resharper.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [2026-3](<https://devfeed.tech/tags/2026-3.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [c-26](<https://devfeed.tech/tags/c-26.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [c-plus-plus-26](<https://devfeed.tech/tags/c-plus-plus-26.md>), [class](<https://devfeed.tech/tags/class.md>), [code-analysis](<https://devfeed.tech/tags/code-analysis.md>), [cpp](<https://devfeed.tech/tags/cpp.md>), [cuda](<https://devfeed.tech/tags/cuda.md>), [fmt](<https://devfeed.tech/tags/fmt.md>), [format](<https://devfeed.tech/tags/format.md>), [include](<https://devfeed.tech/tags/include.md>), [layout](<https://devfeed.tech/tags/layout.md>), [memory](<https://devfeed.tech/tags/memory.md>), [net-tools](<https://devfeed.tech/tags/net-tools.md>), [news](<https://devfeed.tech/tags/news.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [resharper](<https://devfeed.tech/tags/resharper.md>), [resharper-c](<https://devfeed.tech/tags/resharper-c.md>), [resharper-c-plus-plus](<https://devfeed.tech/tags/resharper-c-plus-plus.md>), [resharpercplusplus](<https://devfeed.tech/tags/resharpercplusplus.md>), [std-format](<https://devfeed.tech/tags/std-format.md>), [string](<https://devfeed.tech/tags/string.md>), [tool](<https://devfeed.tech/tags/tool.md>), [updates](<https://devfeed.tech/tags/updates.md>), [window](<https://devfeed.tech/tags/window.md>)

### AI overview

ReSharper C++ 2026.3 adds a Class Layout window that shows field and bit-field offsets and sizes, base subobjects, virtual table pointers, and padding, helping inspect object size and the effects of alignment or packing. Format-string analysis now covers standard `std::format`/`std::print`, {fmt}, C23 `printf` specifiers, POSIX positional arguments, and Unreal Engine structured logging, with checks for invalid fields, argument mismatches, and type specifications. Constructor Change Signature updates many call forms but may miss implicit conversions and custom factory templates. Other additions include configurable Extract Method placement, `constexpr` extraction, CUDA inspections, and explanations for failed constraints. The excerpt also reports updates to Clang-Tidy and Visual Studio integration.

### Source excerpt

ReSharper C++ 2026.3 is here, with a new Class Layout tool window that visualizes the memory layout of your classes and helps you spot wasted space.. This release also improves format string analysis to cover std::format, std::print, and the {fmt} library. Other highlights include updates to the Change Signature and Extract Method refactorings, as well [...]

## An Empirical Analysis of Static Analysis Methods for Detection and Mitigation of Code Library Hallucinations

DevFeed: [An Empirical Analysis of Static Analysis Methods for Detection and Mitigation of Code Library Hallucinations](<https://devfeed.tech/articles/an-empirical-analysis-of-static-analysis-methods-for-detection-and-mitigation-of-code-library-hallucinations-124002.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2604.07755>)

Author: Clarissa Miranda-Pena, Andrew Reeson, C\\'ecile Paris, Josiah Poon, Jonathan K. Kummerfeld

Published: 2026-11-09T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [code](<https://devfeed.tech/tags/code.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [detection](<https://devfeed.tech/tags/detection.md>), [errors](<https://devfeed.tech/tags/errors.md>), [hallucinations](<https://devfeed.tech/tags/hallucinations.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [library](<https://devfeed.tech/tags/library.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [performance](<https://devfeed.tech/tags/performance.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>)

### AI overview

On NL-to-code benchmarks requiring library use, 8.1-40% of LLM responses used non-existent library features. The paper finds static analysis detects 14-85% of library hallucinations and 16-70% of errors overall, with results varying by model and dataset. Manual analysis estimates that 48.5-77% is the upper bound on what static methods could plausibly catch, indicating they can address some cases but cannot solve the problem.

### Source excerpt

arXiv:2604.07755v3 Announce Type: replace-cross Abstract: Despite extensive research, Large Language Models continue to hallucinate when generating code, particularly when using libraries. On NL-to-code benchmarks that require library use, we find that LLMs generate code that uses non-existent library features in 8.1-40% of responses. One intuitive approach for detection and mitigation of hallucinations is static analysis. In this paper, we analyse the potential of static analysis tools, both in terms of what they can solve and what they cannot. We find that static analysis tools can detect 16-70% of all errors, and 14-85% of library hallucinations, with performance varying by LLM and dataset. Through manual analysis, we identify cases a static method could not plausibly catch, which gives an upper bound on their potential from 48.5% to 77%. Overall, we show that static analysis methods are cheap method for addressing some forms of hallucination, and we quantify how far short of solving the problem they will always be.

## How Grab Improved Mobile App Stability by Safely Handling Surge in AI-Generated Code Changes

DevFeed: [How Grab Improved Mobile App Stability by Safely Handling Surge in AI-Generated Code Changes](<https://devfeed.tech/articles/how-grab-improved-mobile-app-stability-by-safely-handling-surge-in-ai-generated-code-changes-122001.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/grab-ai-generated-code-safety/>)

Author: Sergio De Simone

Published: 2026-11-07T11:00:00Z

Content type: article

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Android](<https://devfeed.tech/topics/android.md>), [ai slop pull requests](<https://devfeed.tech/topics/ai-slop-pull-requests.md>)

Tags: [accelerated](<https://devfeed.tech/tags/accelerated.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [app-stability](<https://devfeed.tech/tags/app-stability.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-assistants](<https://devfeed.tech/tags/coding-assistants.md>), [contain](<https://devfeed.tech/tags/contain.md>), [continuous-improvement](<https://devfeed.tech/tags/continuous-improvement.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [development](<https://devfeed.tech/tags/development.md>), [feature-toggle](<https://devfeed.tech/tags/feature-toggle.md>), [grab](<https://devfeed.tech/tags/grab.md>), [grab-ai-generated-code-safety](<https://devfeed.tech/tags/grab-ai-generated-code-safety.md>), [handling](<https://devfeed.tech/tags/handling.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app](<https://devfeed.tech/tags/mobile-app.md>), [news](<https://devfeed.tech/tags/news.md>), [runtime-analytics](<https://devfeed.tech/tags/runtime-analytics.md>), [safely](<https://devfeed.tech/tags/safely.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Grab manages the higher volume of changes associated with AI coding assistants through layered crash defenses across the release lifecycle. Before merge, Android Lint, SwiftLint, tests, QA, and Grab Early Access (GEA) aim to catch problems early; GEA builds are distributed to internal users and monitored for crashes. During release, staged rollouts limit initial exposure and can be paused if crash rates rise, while feature flags allow individual features to be activated gradually or disabled when predefined crash thresholds are exceeded. After release, Firebase Crashlytics and BigQuery support real-time anomaly detection; aggregated crash metadata and stack traces help teams trace incidents to specific PRs. Post-mortems feed findings back into lint rules and test coverage. The excerpt presents prevention as the primary defense and notes that shipped crashes can persist on devices where users do not automatically update.

### Source excerpt

The growing adoption of AI coding assistants has accelerated development and increased the volume of code changes per release, bringing more opportunities for defects and crashes, says Grab. To address these challenges, they implemented a layered defense strategy to prevent, detect, and contain crashes throughout the development and release lifecycle. By Sergio De Simone

## Introducing Svet: A Git Repository Linter

DevFeed: [Introducing Svet: A Git Repository Linter](<https://devfeed.tech/articles/introducing-svet-a-git-repository-linter-110590.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/10/31/introducing-svet-a-git-repository-linter.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-10-31T00:00:00Z

Content type: release

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [lint](<https://devfeed.tech/topics/lint.md>), [Git](<https://devfeed.tech/topics/git.md>), [ESLint](<https://devfeed.tech/topics/eslint.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Prettier](<https://devfeed.tech/topics/prettier.md>)

Tags: [eslint](<https://devfeed.tech/tags/eslint.md>), [git](<https://devfeed.tech/tags/git.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lint](<https://devfeed.tech/tags/lint.md>), [linter](<https://devfeed.tech/tags/linter.md>), [nodejs](<https://devfeed.tech/tags/nodejs.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [portable](<https://devfeed.tech/tags/portable.md>), [pre-commit](<https://devfeed.tech/tags/pre-commit.md>), [repository](<https://devfeed.tech/tags/repository.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Svet is a JavaScript repository linter that separates file selection from checks, so checks can use both file contents and Git path metadata without requiring a language parser. Its default Git selector checks tracked text files for LF endings and includes binary paths in the inventory used for filename checks. The `--precommit` mode checks staged Git-index snapshots without staging, stashing, or fixing files; revision comparisons use target-commit contents and do not fetch branches. Separate plugins provide checks such as trailing whitespace and path case. The excerpt contrasts this with an ESLint portability plugin that detects case and Unicode-normalization collisions, Windows-invalid names, and configurable path-length limits, but sees the current filesystem rather than staged snapshots and cannot fix filesystem names.

### Source excerpt

The idea for Svet came from a private repository at work, where checking filename case helps catch portability problems like Logo.svg and logo.svg colliding on a case-insensitive Windows filesystem. These checks are implemented in pure JavaScript. That seemed like a useful job for a reusable repository linter. I went looking for an existing tool. Tool Why it isn't enough here ESLint Can check filenames with a processor; byte-level checks and Git snapshots need custom plumbing. Oxlint Arbitrary non-JS/TS files don't reach its lint rules. Biome Checks supported languages, not arbitrary repository files. Stylelint Built for stylesheet rules; repository-wide checks need custom code. markdownlint-cli2 Can check filenames, but Markdown parsing isn't a byte-level checking API. HTML-validate Requires HTML or template transformations, not a general file-checking API. Prettier Skips or rejects unsupported formats; doesn't check repository-wide path rules. lint-staged Can run the checks, but doesn't supply rules or Git-index snapshots itself. Prettier is a formatter, and lint-staged is a task runner. They're in this list because they also appear in development and CI workflows. The important distinction is selecting a path, checking its name, understanding its contents, and choosing which version of those contents to inspect. Those are four different things. I built Svet for that job. Then I doubted myself and took a detour extending ESLint with eslint-plugin-portable-paths. It checks four portability problems: case-insensitive file and directory collisions, Unicode-normalization collisions, Windows-invalid names such as NUL.txt, and paths or individual names exceeding configurable lengths. It's almost everything. The remaining limitations of the eslint approach are about which files and bytes we're checking. This plugin sees the current filesystem, including untracked paths, and is not Git-aware, so a pre-commit hook would check the working tree, not the staged snapshot. ESLi

## The Hitchhiker's Guide to Program Analysis, Part III: Mostly Harmless LLMs

DevFeed: [The Hitchhiker's Guide to Program Analysis, Part III: Mostly Harmless LLMs](<https://devfeed.tech/articles/the-hitchhiker-s-guide-to-program-analysis-part-iii-mostly-harmless-llms-94601.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.15122>)

Author: Haonan Li, Tianyang Zhou, Manu Sridharan, Hang Zhang, Zhiyun Qian

Published: 2026-10-22T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [driver](<https://devfeed.tech/tags/driver.md>), [flow](<https://devfeed.tech/tags/flow.md>), [harness](<https://devfeed.tech/tags/harness.md>), [llms](<https://devfeed.tech/tags/llms.md>), [manual-review](<https://devfeed.tech/tags/manual-review.md>), [program-analysis](<https://devfeed.tech/tags/program-analysis.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>), [validation](<https://devfeed.tech/tags/validation.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Evident uses LLMs to find relevant code and build a harness for targeted Frama-C/Eva analysis, leaving the decision to filter a warning to the sound static analyzer. Since a harness could omit paths or inputs that trigger bugs, Evident restricts input initialization and checks the harness against value flow from the original detector; it filters a warning only if validation passes and Eva rules out the reported error. On 200 Android kernel-driver warnings, including 40 confirmed bugs, it filtered 48.8-63.8% of 160 false alarms across four LLMs without missing a confirmed bug. Baselines that let LLMs decide missed confirmed bugs with every evaluated model. With GPT-5.5, those baselines had 2.0-5.5 percentage points higher overall accuracy but missed 27.5-45.0% of confirmed bugs. Evident also rediscovered a confirmed vulnerability previously missed by LLM-based filtering and manual review.

### Source excerpt

arXiv:2606.15122v2 Announce Type: replace Abstract: Filtering out a static-analysis warning asserts that no feasible execution can trigger the reported error, whereas confirming a bug requires only one that does. Recent work uses LLMs to filter out warnings. However, LLM-generated explanations alone cannot establish that the reported error is impossible, and mistakenly filtering out a warning conceals a real bug. Sound static analysis can provide this guarantee, but scalable analyses leave behind the very warnings we seek to filter, whereas sufficiently precise whole-program analysis is impractical. Fortunately, analyzing a small part of the program is often enough to show that a warning is a false alarm. We therefore assign LLMs a different role: rather than judging the validity of warnings, they identify relevant code and construct a harness that supplies the context needed for precise, targeted static analysis. We present Evident, which combines LLMs with the static analyzer Frama-C/Eva. Because a generated harness may exclude inputs or paths that trigger real bugs, Evident restricts how the harness initializes inputs and validates it using the value flow reported by the original detector. A warning is filtered out only when validation passes and Eva rules out the reported error in the harness; otherwise, the warning is kept. On 200 real Android kernel-driver warnings, including 40 confirmed bugs, Evident filters out 48.8-63.8% of the 160 false alarms across four LLMs without missing any confirmed bug, whereas baselines that let LLMs make the final decision miss confirmed bugs with every evaluated model. With GPT-5.5, although these baselines achieve 2.0-5.5 percentage points higher overall accuracy by filtering out more false alarms, they miss 27.5-45.0% of the confirmed bugs. Evident also rediscovers a confirmed vulnerability that had previously been overlooked by both LLM-based filtering and manual review.

## Testing AI-Generated Code: Lint the Pattern, Test the Decision

DevFeed: [Testing AI-Generated Code: Lint the Pattern, Test the Decision](<https://devfeed.tech/articles/testing-ai-generated-code-lint-the-pattern-test-the-decision-92573.md>)

Original publisher: [Read original article](<https://www.robinwieruch.de/testing-ai-generated-code/>)

Author: Robin Wieruch

Published: 2026-10-21T06:50:46Z

Content type: article

Language: en

Sources: [Robin Wieruch](<https://devfeed.tech/sources/robin-wieruch.md>)

Topics: [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [lint](<https://devfeed.tech/topics/lint.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [coding patterns](<https://devfeed.tech/topics/coding-patterns.md>)

Tags: [agentic-engineering](<https://devfeed.tech/tags/agentic-engineering.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-engineer](<https://devfeed.tech/tags/ai-engineer.md>), [ai-generated-tests](<https://devfeed.tech/tags/ai-generated-tests.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [lint](<https://devfeed.tech/tags/lint.md>), [lint-rules-for-ai-agents](<https://devfeed.tech/tags/lint-rules-for-ai-agents.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [software-factory](<https://devfeed.tech/tags/software-factory.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [testing-ai-generated-code](<https://devfeed.tech/tags/testing-ai-generated-code.md>)

### AI overview

The article's approach is to enforce each file type's documented skeleton with lint, centralize test setup in a shared harness, and test only files that make decisions beyond that pattern. For handlers, lint checks session-first ordering, service calls inside try/catch, error mapping, and safe input flow; it covers every handler and makes tests for those invariants redundant. A shared harness fakes external effects and uses the real generated backend client over an in-memory transport, with safeguards for unserved methods, fake crashes, and production request limits. Tests focus on requests, results, side effects, branches, security choices, and failure behavior. The approach also applies to forms and comboboxes, while some file types need no harness or individual tests. It targets useful unit and integration coverage, not a fully tested codebase; end-to-end testing is outside the article's scope.

### Source excerpt

Testing AI-generated code without the noise: lint the patterns coding agents follow, share one test harness, and add tests only where a file leaves its pattern.

## Your Design System Is a Contract. Enforce It with Konsist and Android Lint

DevFeed: [Your Design System Is a Contract. Enforce It with Konsist and Android Lint](<https://devfeed.tech/articles/your-design-system-is-a-contract-enforce-it-with-konsist-and-android-lint-91135.md>)

Original publisher: [Read original article](<https://proandroiddev.com/konsist-design-system-validator-jetpack-compose-d5c3814fe462?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-10-20T16:36:52Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Design system](<https://devfeed.tech/topics/design-system.md>), [lint](<https://devfeed.tech/topics/lint.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [automated](<https://devfeed.tech/tags/automated.md>), [color](<https://devfeed.tech/tags/color.md>), [colors](<https://devfeed.tech/tags/colors.md>), [component](<https://devfeed.tech/tags/component.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-ui](<https://devfeed.tech/tags/compose-ui.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [custom](<https://devfeed.tech/tags/custom.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [design-systems](<https://devfeed.tech/tags/design-systems.md>), [dimensions](<https://devfeed.tech/tags/dimensions.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [feature](<https://devfeed.tech/tags/feature.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [lint](<https://devfeed.tech/tags/lint.md>), [padding](<https://devfeed.tech/tags/padding.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [rules](<https://devfeed.tech/tags/rules.md>), [screen](<https://devfeed.tech/tags/screen.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

Treat the design system as an enforceable engineering contract: centralize approved tokens and reusable components, then place each rule in the layer suited to check it. Konsist can test package structure and architectural boundaries; custom Android Lint detectors can flag prohibited source patterns, such as numeric Compose Color literals outside approved packages; Compose UI tests can check rendered behavior like accessibility, font scaling, touch targets, and state transitions. The sample Lint rule is deliberately limited: it may miss colors expressed through constants, helpers, resources, aliases, or other forms, and it cannot judge whether a named token is semantically appropriate. The article recommends testing both violations and allowed exceptions, keeping rules narrow to reduce false positives, verifying APIs against the project's pinned versions, and rolling checks out gradually before making them blocking in CI.

### Source excerpt

A practical guide to enforcing colors, spacing, typography, shapes, and component conventions in Jetpack Compose -- with a custom Android Lint rule. A design system is only as reliable as the rules that prevent teams from bypassing it. Most Android teams have a design system. They define typography, colors, spacing, shapes, dimensions, and reusable Compose components. They document usage guidelines, publish component libraries, and ask developers to follow the established conventions. Yet a few months into development, the same problems start appearing. One screen uses 16.dp for horizontal padding; another uses 18.dp. A developer creates a custom TextStyle because the existing typography does not look quite right. A feature introduces a hardcoded hex color. A button uses a different corner radius from the rest of the application. Someone builds another card component because the existing one seems inconvenient to reuse. None of these decisions looks particularly dangerous in isolation. Together, they undermine the consistency the design system was supposed to provide. Code reviews can catch some of these violations, but they are not a reliable enforcement mechanism. Reviewers have limited time, conventions are easy to overlook, and the same feedback gets repeated across pull requests. The better approach is to treat the design system as an engineering contract and enforce that contract through automated checks. For Android teams using Jetpack Compose, Konsist and custom Android Lint rules solve complementary parts of this problem. Konsist can enforce architectural and structural conventions. Android Lint can inspect source code for prohibited patterns. Compose UI tests can verify how the resulting interface behaves at runtime. Together, they turn design-system conventions from documentation into executable rules. Start by defining what the contract actually means Before writing a test or a lint detector, identify the rules your team expects every feature to follow. N

## Codebase Design for AI Agents: Types, Lint Rules, and CI Gates

DevFeed: [Codebase Design for AI Agents: Types, Lint Rules, and CI Gates](<https://devfeed.tech/articles/codebase-design-for-ai-agents-types-lint-rules-and-ci-gates-90890.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/codebase-design-for-ai-agents/>)

Author: SitePoint Team

Published: 2026-10-20T15:44:18Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Programming Language Type Systems](<https://devfeed.tech/topics/programming-language-type-systems.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [identifier](<https://devfeed.tech/topics/identifier.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-framework](<https://devfeed.tech/tags/agent-framework.md>), [agent-frameworks](<https://devfeed.tech/tags/agent-frameworks.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ast](<https://devfeed.tech/tags/ast.md>), [ci](<https://devfeed.tech/tags/ci.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [eslint](<https://devfeed.tech/tags/eslint.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lint](<https://devfeed.tech/tags/lint.md>), [programming](<https://devfeed.tech/tags/programming.md>), [rules](<https://devfeed.tech/tags/rules.md>), [structure](<https://devfeed.tech/tags/structure.md>), [types](<https://devfeed.tech/tags/types.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

The tutorial's central takeaway is to make correct code paths enforceable so AI-generated code must satisfy repository constraints. It layers four guardrails: branded TypeScript types with validated constructors reject raw identifiers at compile time (though direct casts can bypass them); custom AST-based ESLint rules enforce architectural boundaries, with RuleTester fixtures showing permitted and forbidden imports; sequential CI checks type-checking, lint, and tests, while branch protection makes passing checks a merge requirement; and AGENTS.md documents conventions for supported agents but remains a soft guide that can be truncated or misread. The examples require Node.js 20+ and ESLint v9 flat config. The article recommends starting with a critical identifier and a frequently violated boundary, then expanding and maintaining the guidance as the codebase changes.

### Source excerpt

Structure TypeScript repos to constrain AI coding agents with compile-time branded types, AST-based ESLint rules, CI gates, and focused AGENTS.md files. Continue reading Codebase Design for AI Agents: Types, Lint Rules, and CI Gates on SitePoint.

## Static Analysis for the Uninitialized

DevFeed: [Static Analysis for the Uninitialized](<https://devfeed.tech/articles/static-analysis-for-the-uninitialized-89926.md>)

Original publisher: [Read original article](<https://tenderlovemaking.com/2026/10/18/static-analysis-for-the-uninitialized/>)

Published: 2026-10-19T03:20:26Z

Content type: tutorial

Language: en

Sources: [Aaron Patterson](<https://devfeed.tech/sources/aaron-patterson.md>)

Topics: [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Snowflake streaming data architecture](<https://devfeed.tech/topics/snowflake-streaming-data-architecture.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [if-statement](<https://devfeed.tech/tags/if-statement.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [program-analysis](<https://devfeed.tech/tags/program-analysis.md>), [programming](<https://devfeed.tech/tags/programming.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>)

### AI overview

The article walks through a static analysis for finding possibly uninitialized variables. It models data flow with bipartite graphs, implements the analysis in Ruby, and applies it to TIP and Ruby code, including a forward analysis over a control flow graph.

### Source excerpt

I really enjoy learning new things in my free time. Lately I've been studying this book on Static Program Analysis. The book is very good, but some of the formulas are quite dense so I like to try writing them out in code. The chapter I'm currently reading (chapter 9) has a section on finding possibly-uninitialized variables using bipartite graphs. I've found it to be quite enjoyable, so in this post I would like to describe, in my own words, how to do it. We'll start by analyzing some code from a toy programming language the book uses called "TIP", and then we'll use the techniques we developed to analyze some Ruby code. In other words, we're going to write a program to analyze programs. We're really going to be meta-programmers today! Uninitialized variables in TIP The TIP programming language is like a very very simplified version of JavaScript. Below is the code we'll be analyzing: var a, b, c; // a, b, c a = input; // b, c b = a + c; // b, c if (input) { // b, c c = 1; // b } // b, c This example is taken straight from the chapter. In TIP, you declare variables with the var keyword kind of like in JavaScript. In chapter 9 of the book, the TIP language only has integers; later chapters add pointers. In TIP, 0 is considered false, and there is a special function input that returns an integer input from the user. Each line in the above code has a comment indicating which variables are possibly uninitialized. I keep saying "possibly", and I'll explain why later. The first line declares the variables with var, and all variables start as "uninitialized" when they are declared. The second line gets input and assigns it to a, so now only b and c are uninitialized. The third line adds a and c and assigns it to b. On this line, b is still considered to be "uninitialized" because c is uninitialized, and the value of b depends on the values of a and c. The fourth line is an if statement, and whether we take the if statement depends on input from the user. In other words, w

## Rapid7 Analysis: GitLab CI/CD Regex Integer Overflow (CVE-2026-97229)

DevFeed: [Rapid7 Analysis: GitLab CI/CD Regex Integer Overflow (CVE-2026-97229)](<https://devfeed.tech/articles/rapid7-analysis-gitlab-ci-cd-regex-integer-overflow-cve-2026-97229-88757.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ra-gitlab-ci-cd-regex-integer-overflow-technical-analysis-cve-2026-97229>)

Author: Jonah Burgess

Published: 2026-10-16T13:31:56Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Regular expression](<https://devfeed.tech/topics/regular-expression.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [code analysis](<https://devfeed.tech/topics/code-analysis.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [integer-overflow](<https://devfeed.tech/tags/integer-overflow.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [rapid7-analysis](<https://devfeed.tech/tags/rapid7-analysis.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [regex](<https://devfeed.tech/tags/regex.md>), [research](<https://devfeed.tech/tags/research.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

GitLab fixed CVE-2026-97229 in releases 19.2.8, 19.3.5, and 19.4.2. Rapid7's PoC chains an unchecked UTF-8 recompilation of attacker-controlled regex pcode with a signed integer overflow in Onigmo, redirecting execution to run commands as GitLab's `git` account. The demonstrated route requires malicious CI configuration and a specially named path already pushed to a public project; only the final CI lint request is unauthenticated, a prerequisite the researchers say conflicts with GitLab's PR:N rating. The PoC worked on Linux amd64 GitLab CE 19.4.1 with ASLR, but needs target-specific offsets and substantial memory. Self-managed users are advised to upgrade; temporarily restricting credential-free access to attacker-writable public projects or blocking the lint route may mitigate exposure. The Ruby fix prevents overflow in the compiler size check and limits compiled program size.

### Source excerpt

Overview On October 12, 2026, GitLab released 19.4.2, 19.3.5, and 19.2.8 to fix CVE-2026-97229, an integer overflow in its CI/CD regular-expression handling. The issue was reported through HackerOne by joaxcar. GitLab assigned it a CVSS score of 10.0 and described possible code execution by an unauthenticated user. The advisory states that CVE-2026-97229 affects GitLab CE and EE from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. GitLab says all deployment types are affected unless stated otherwise. GitLab.com was patched before disclosure, and Dedicated customers do not need to act. Rapid7 researchers developed an end-to-end PoC that reliably runs arbitrary commands as GitLab's git operating-system account on the official Linux amd64 gitlab/gitlab-ce:19.4.1-ce.0 image with ASLR enabled. GitLab's release notes do not report exploitation in the wild occurring at the time of disclosure. This analysis covers one end-to-end route. It begins after an attacker has pushed both the malicious CI configuration and a specially named path to a public project; only the final CI lint request is unauthenticated. That prerequisite conflicts with GitLab's PR:N rating, and because the underlying report remains private, we do not yet know how the reported attack avoids it. Technical analysis At a high level, the chain crosses from attacker-controlled repository input into Onigmo pcode and finally native code execution. Figure 1: From repository inputs to command execution. CI rules pass repository paths to Onigmo GitLab supports regular-expression matching over repository paths in rules:exists:regexp and rules:changes:regexp. One way to evaluate such an expression during static configuration processing is to place it on a conditional include: include: - local: /benign.yml rules: - exists: regexp: "ATTACKER_PATTERN" RegexpMatcher expands the expression, compiles it with Ruby's native regular-expression engine, and tests it against paths from the selected Git worktree:

## Tracking execution events for your WorkManager Workers

DevFeed: [Tracking execution events for your WorkManager Workers](<https://devfeed.tech/articles/tracking-execution-events-for-your-workmanager-workers-60130.md>)

Original publisher: [Read original article](<https://msfjarvis.dev/posts/tracking-execution-events-for-your-workmanager-workers/>)

Author: Harsh Shandilya

Published: 2026-09-25T11:05:00Z

Content type: tutorial

Language: en

Sources: [Posts on Harsh Shandilya](<https://devfeed.tech/sources/posts-on-harsh-shandilya.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [execution](<https://devfeed.tech/topics/execution.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Sentry](<https://devfeed.tech/topics/sentry.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [android](<https://devfeed.tech/tags/android.md>), [android-jetpack](<https://devfeed.tech/tags/android-jetpack.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [execution](<https://devfeed.tech/tags/execution.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [lint](<https://devfeed.tech/tags/lint.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [sentry](<https://devfeed.tech/tags/sentry.md>), [workmanager](<https://devfeed.tech/tags/workmanager.md>)

### AI overview

A tutorial on using new experimental WorkManager APIs in Android Jetpack to inspect worker executions, collect execution metrics, and send events to Sentry dashboards. It also discusses limitations involving result subtypes, Lint, and Kotlin parameters.

### Source excerpt

WorkManager 2.12.0 introduces brand new APIs for deep introspection of Worker executions

## Difflock: Lint Laravel Migrations and Diff Your Schema

DevFeed: [Difflock: Lint Laravel Migrations and Diff Your Schema](<https://devfeed.tech/articles/difflock-lint-laravel-migrations-and-diff-your-schema-55738.md>)

Original publisher: [Read original article](<https://laravel-news.com/difflock-migration-linter>)

Author: Yannick Lyn Fatt

Published: 2026-09-20T20:52:18Z

Content type: article

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [migration](<https://devfeed.tech/topics/migration.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Database](<https://devfeed.tech/topics/database.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [database](<https://devfeed.tech/tags/database.md>), [json](<https://devfeed.tech/tags/json.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-packages](<https://devfeed.tech/tags/laravel-packages.md>), [lint](<https://devfeed.tech/tags/lint.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

Difflock is a Laravel package that reviews database migrations against live schema and table-size metadata. It flags risky changes, records JSON schema baselines, detects schema drift, and supports migration checks in CI and through MCP tools.

### Source excerpt

Difflock is a Laravel package that checks pending migrations for risky changes, records schema baselines, and can block them in CI. The post Difflock: Lint Laravel Migrations and Diff Your Schema appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## Using static analysis in Python, JavaScript and more to make your system safer

DevFeed: [Using static analysis in Python, JavaScript and more to make your system safer](<https://devfeed.tech/articles/using-static-analysis-in-python-javascript-and-more-to-make-your-system-safer-27419.md>)

Original publisher: [Read original article](<http://engineering.khanacademy.org/posts/using-static-analysis-in-Python-and-JavaScript-to-make-your-system-safer.htm>)

Author: Khan Academy

Published: 2018-07-26T22:00:00Z

Content type: article

Language: en

Sources: [Khan Academy](<https://devfeed.tech/sources/khan-academy.md>)

Topics: [lint](<https://devfeed.tech/topics/lint.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [ESLint](<https://devfeed.tech/topics/eslint.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lint](<https://devfeed.tech/tags/lint.md>), [linting](<https://devfeed.tech/tags/linting.md>), [news](<https://devfeed.tech/tags/news.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

Khan Academy's custom linters catch repository-specific problems beyond formatting: mismatched duplicated code across JavaScript, Python, and Kotlin; newly added legacy Handlebars or LESS files; team photos with inconsistent dimensions; duplicate Python test names that can silently replace tests; GraphQL queries that diverge from server expectations; and disallowed Python imports. Some checks use whitelists to accommodate existing files while cleanup continues. The author recommends regular expressions when they are sufficient and faster than parsers, while warning they may mishandle real-world code; unit tests can verify expected cases.

### Source excerpt

By Kevin Dangoor "Linting" source code to look for errors is nothing new (the original "lint" tool turned ... Read more

## AGENTS.md Optimization: Cut Token Waste with Automated Linting

DevFeed: [AGENTS.md Optimization: Cut Token Waste with Automated Linting](<https://devfeed.tech/articles/agents-md-optimization-cut-token-waste-with-automated-linting-50801.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/agents-md-optimization-cut-token-waste-linting/>)

Author: SitePoint Team

Published: 2026-09-10T19:34:42Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [context window](<https://devfeed.tech/topics/context-window.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>), [monorepo](<https://devfeed.tech/topics/monorepo.md>)

Tags: [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [ast](<https://devfeed.tech/tags/ast.md>), [ci](<https://devfeed.tech/tags/ci.md>), [coding](<https://devfeed.tech/tags/coding.md>), [context](<https://devfeed.tech/tags/context.md>), [devops](<https://devfeed.tech/tags/devops.md>), [lint](<https://devfeed.tech/tags/lint.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

A tutorial on reducing token waste in AGENTS.md files through auditing, deduplication, concise rules, removal of obsolete instructions, scoped nested files, and automated Markdown AST linting in CI. It also describes token budgets and usage tracking.

### Source excerpt

Learn how to optimize AGENTS.md files and implement automated context linting to reduce token waste across autonomous coding agent sessions. Continue reading AGENTS.md Optimization: Cut Token Waste with Automated Linting on SitePoint.

## Four Mechanisms Behind EGP Code, an AI-Powered Landing Page Editor

DevFeed: [Four Mechanisms Behind EGP Code, an AI-Powered Landing Page Editor](<https://devfeed.tech/articles/four-mechanisms-behind-egp-code-an-ai-powered-landing-page-editor-56815.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20260610-how-egp-code-works/>)

Author: Mattsuu

Published: 2026-06-10T11:00:58Z

Content type: article

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Firestore](<https://devfeed.tech/topics/firestore.md>), [data](<https://devfeed.tech/topics/data.md>), [test](<https://devfeed.tech/topics/test.md>), [API](<https://devfeed.tech/topics/api.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [css](<https://devfeed.tech/tags/css.md>), [errors](<https://devfeed.tech/tags/errors.md>), [firestore](<https://devfeed.tech/tags/firestore.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [lint](<https://devfeed.tech/tags/lint.md>)

### AI overview

This article explains four mechanisms inside EGP Code, Merpay's internal AI editor for building landing pages: a recursive agent loop, real-time synchronization through Firestore, browser-based testing, and a mapping table connecting preview elements to HTML. It also describes how the editor combines AI instructions, manual HTML editing, previewing, and publishing.

### Source excerpt

Hi, I'm @mattsuu a frontend engineer at Merpay. This is Day 7 of Merpay & Mercoin Tech Openness Month 2026. EGP Code is an internal editor for building landing pages (LPs) with AI. We covered the background in Why we built EGP Code, an HTML-based AI editor for landing pages; this article digs into four [...]

## CodeQL 2.25.3 adds Swift 6.3 support

DevFeed: [CodeQL 2.25.3 adds Swift 6.3 support](<https://devfeed.tech/articles/codeql-2-25-3-adds-swift-6-3-support-71806.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-05-08-codeql-2-25-3-adds-swift-6-3-support>)

Author: Allison

Published: 2026-05-08T09:02:12Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [c-c-plus-plus](<https://devfeed.tech/tags/c-c-plus-plus.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [code-scanning](<https://devfeed.tech/tags/code-scanning.md>), [codeql](<https://devfeed.tech/tags/codeql.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [java](<https://devfeed.tech/tags/java.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swift-6-3](<https://devfeed.tech/tags/swift-6-3.md>)

### AI overview

CodeQL 2.25.3 adds Swift 6.3 analysis and Python extraction for PEP-810 lazy imports. It promotes five C/C++ queries to high precision and the default code scanning suite; `cpp/implicit-function-declaration` no longer reports on `build-mode: none` databases because those results were noisy and imprecise. Other changes include expanded Java/Kotlin XXE sink detection for Woodstox, improved precision or fewer false positives in several C#, JavaScript/TypeScript, Python, and GitHub Actions queries, and updated alert messages and locations for artifact-poisoning alerts. The release is automatically deployed to GitHub.com code scanning and is slated for GHES 3.22; users of older GHES versions can upgrade CodeQL manually.

### Source excerpt

CodeQL is the static analysis engine behind GitHub code scanning, which finds and remediates security issues in your code. We've recently released CodeQL 2.25.3, which adds support for Swift 6.3,...

## Linting, Automated: AI-Powered Static Analysis with Gemini

DevFeed: [Linting, Automated: AI-Powered Static Analysis with Gemini](<https://devfeed.tech/articles/linting-automated-ai-powered-static-analysis-with-gemini-24911.md>)

Original publisher: [Read original article](<https://blog.blundellapps.co.uk/linting-automated-ai-powered-static-analysis-with-gemini/>)

Author: blundell

Published: 2025-09-23T16:24:26Z

Content type: tutorial

Language: en

Sources: [Blundell](<https://devfeed.tech/sources/blundell.md>)

Topics: [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [detekt](<https://devfeed.tech/topics/detekt.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [automated](<https://devfeed.tech/tags/automated.md>), [detekt](<https://devfeed.tech/tags/detekt.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [intermediate](<https://devfeed.tech/tags/intermediate.md>), [linting](<https://devfeed.tech/tags/linting.md>), [python](<https://devfeed.tech/tags/python.md>), [reference](<https://devfeed.tech/tags/reference.md>), [reference-ai-androiddev-detekt-gemini](<https://devfeed.tech/tags/reference-ai-androiddev-detekt-gemini.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>)

### AI overview

The excerpt describes using a Python script with Google's Gemini to automate fixes for static analysis findings such as Detekt, Checkstyle, and ESLint. It begins with a one-shot approach: provide the model with the lint output and affected files, then ask it to fix the issues. The main constraint is context-window size; bundling findings and several full files can exceed model limits. The excerpt contrasts GPT-4 Turbo's stated 128,000-token and Claude 3.5 Sonnet's 200,000-token windows with Gemini 2.5's stated 1-million-token window, which allows richer context in many common scenarios. The text ends as it begins a step on curating context and counting tokens, so it does not establish the eventual implementation or results.

### Source excerpt

Tired of fixing endless linting errors? What if an AI could do it for you? In this post, we'll walk through how to build a Python script that uses Google's Gemini to automatically fix static analysis issues, exploring the process and the lessons learned along the way. This is a journey from a simple idea [...] The post Linting, Automated: AI-Powered Static Analysis with Gemini first appeared on Blundell.

## GitHub CLI 2.75.1

DevFeed: [GitHub CLI 2.75.1](<https://devfeed.tech/articles/github-cli-2-75-1-75178.md>)

Original publisher: [Read original article](<https://github.com/cli/cli/releases/tag/v2.75.1>)

Published: 2025-07-14T21:51:23Z

Content type: release

Language: en

Sources: [GitHub CLI](<https://devfeed.tech/sources/github-cli.md>)

Topics: [GitHub CLI extension](<https://devfeed.tech/topics/gh-extension.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [lint](<https://devfeed.tech/topics/lint.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [codeql](<https://devfeed.tech/tags/codeql.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [github](<https://devfeed.tech/tags/github.md>), [github-cli](<https://devfeed.tech/tags/github-cli.md>), [go](<https://devfeed.tech/tags/go.md>), [lint](<https://devfeed.tech/tags/lint.md>), [sigstore](<https://devfeed.tech/tags/sigstore.md>)

### AI overview

GitHub CLI 2.75.1 includes a fix to display hostnames in the CLI website, documentation and maintenance changes, CodeQL and golangci-lint filtering updates, and dependency upgrades including Go 1.24.5.

### Source excerpt

## What's Changed ### 🐛 Fixes * Ensure hostnames are visible in CLI website by @andyfeller in https://github.com/cli/cli/pull/11295 * Revert "Fix: `gh pr create` prioritize `--title` and `--body` over `--fill` when `--web` is present" by @andyfeller in https://github.com/cli/cli/pull/11300 ### 📚 Docs & Chores * Ensure go directive is always .0 version in bump by @williammartin in https://github.com/cli/cli/pull/11259 * Minor (1-word) documentation typo in generated `~/.config/gh/config.yml` by @kurahaupo in https://github.com/cli/cli/pull/11246 * Automate closing of stale issues by @babakks in https://github.com/cli/cli/pull/11268 * Filter the `third-party/` folder out of CodeQL results by @BagToad in https://github.com/cli/cli/pull/11278 * Exclude `third-party` source from golangci-lint by @andyfeller in https://github.com/cli/cli/pull/11293 ### :dependabot: Dependencies * Bump Go to 1.24.5 by @github-actions[bot] in https://github.com/cli/cli/pull/11255 * chore(deps): bump github.com/sigstore/protobuf-specs from 0.4.3 to 0.5.0 by @dependabot[bot] in https://github.com/cli/cli/pull/11263 * chore(deps): bump golang.org/x/term from 0.32.0 to 0.33.0 by @dependabot[bot] in https://github.com/cli/cli/pull/11266 * chore(deps): bump golang.org/x/sync from 0.15.0 to 0.16.0 by @dependabot[bot] in https://github.com/cli/cli/pull/11264 * chore(deps): bump golang.org/x/text from 0.26.0 to 0.27.0 by @dependabot[bot] in https://github.com/cli/cli/pull/11265 * chore(deps): bump golang.org/x/crypto from 0.39.0 to 0.40.0 by @dependabot[bot] in https://github.com/cli/cli/pull/11275 ## New Contributors * @kurahaupo made their first contribution in https://github.com/cli/cli/pull/11246 * @github-actions[bot] made their first contribution in https://github.com/cli/cli/pull/11255 **Full Changelog**: https://github.com/cli/cli/compare/v2.75.0...v2.75.1

## CodeQL 2.17.0: Support for Java 22, Swift 5.10, TS 5.4, C# 12

DevFeed: [CodeQL 2.17.0: Support for Java 22, Swift 5.10, TS 5.4, C# 12](<https://devfeed.tech/articles/codeql-2-17-0-support-for-java-22-swift-5-10-ts-5-4-c-12-73151.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2024-04-11-codeql-2-17-0-support-for-java-22-swift-5-10-ts-5-4-c-12>)

Author: Kevin Duck

Published: 2024-04-11T13:00:25Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Swift](<https://devfeed.tech/topics/swift.md>)

Tags: [22](<https://devfeed.tech/tags/22.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [code-scanning](<https://devfeed.tech/tags/code-scanning.md>), [codeql](<https://devfeed.tech/tags/codeql.md>), [java](<https://devfeed.tech/tags/java.md>), [support](<https://devfeed.tech/tags/support.md>), [swift](<https://devfeed.tech/tags/swift.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

CodeQL 2.17.0 is rolled out to GitHub.com code scanning and adds support for Java 22, Swift 5.10, TypeScript 5.4, and full support for C# 12 and .NET 8. It also improves Go dependency retrieval by up to 27% and adds three queries covering invalid C++ casts, excessive Go slice allocation sizes, and unsafe Java URL construction. C# queries received minor changes for the beta threat model settings feature. The release's functionality is also slated for GHES 3.13; users on GHES 3.12 or older can upgrade their CodeQL version.

### Source excerpt

CodeQL is the static analysis engine that powers GitHub code scanning. CodeQL version 2.17.0 has been released and has now been rolled out to code scanning users on GitHub.com. Important...

## Clojure Deref (Oct 16, 2023)

DevFeed: [Clojure Deref (Oct 16, 2023)](<https://devfeed.tech/articles/clojure-deref-oct-16-2023-49641.md>)

Original publisher: [Read original article](<https://clojure.org/news/2023/10/16/deref>)

Published: 2023-10-16T00:00:00Z

Content type: news

Language: en

Sources: [Clojure News](<https://devfeed.tech/sources/clojure-news.md>)

Topics: [Clojure](<https://devfeed.tech/topics/clojure.md>), [API](<https://devfeed.tech/topics/api.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Data Science](<https://devfeed.tech/topics/data-science.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [ClojureScript](<https://devfeed.tech/topics/clojurescript.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Java](<https://devfeed.tech/topics/java.md>), [lint](<https://devfeed.tech/topics/lint.md>), [React](<https://devfeed.tech/topics/react.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [api](<https://devfeed.tech/tags/api.md>), [backends](<https://devfeed.tech/tags/backends.md>), [builds](<https://devfeed.tech/tags/builds.md>), [caching](<https://devfeed.tech/tags/caching.md>), [clojure](<https://devfeed.tech/tags/clojure.md>), [code](<https://devfeed.tech/tags/code.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data-science](<https://devfeed.tech/tags/data-science.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [imagemagick](<https://devfeed.tech/tags/imagemagick.md>), [java](<https://devfeed.tech/tags/java.md>), [js](<https://devfeed.tech/tags/js.md>), [lint](<https://devfeed.tech/tags/lint.md>), [programming](<https://devfeed.tech/tags/programming.md>), [react](<https://devfeed.tech/tags/react.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scripting](<https://devfeed.tech/tags/scripting.md>), [shell-scripting](<https://devfeed.tech/tags/shell-scripting.md>)

### AI overview

A weekly Clojure ecosystem roundup covering talks, podcasts, articles, projects, libraries, development tools, releases, ClojureScript, and application-development topics.

### Source excerpt

Welcome to the Clojure Deref! This is a weekly link/news roundup for the Clojure ecosystem (feed: RSS). Thanks to Anton Fonarev for link aggregation. Podcasts and videos TMD 7.0 - Higher Performance Functional Data Science (by Chris Nuernberger) - London Clojurians "Babashka: a meta-circular Clojure interpreter for the command line" by Michiel Borkent - Strange Loop Conference Parens of the Dead - Episode 25: Musings on the nature of Christmas mornings - emacsrocks Memoization and Caching Patterns in Clojure: memoize, clojure.core.cache & clojure.core.memoize - Andrey Fadeev Fulcro RAD Multimethod Rendering - Tony Kay Runtime Class Reloading on Mixed Java/Clojure Projects - Tony Kay How to format and lint Clojure code: cljfmt, clj-kondo and Babashka task runner! - Andrey Fadeev Interactive Shell Scripting with Babashka - CalvaTV "A JVM threading model for the containerized times" by Luiz Hespanha and Flavio Brasil - Strange Loop Conference "Computational Physics, Beyond the Glass" by Sam Ritchie (Strange Loop 2023) - Strange Loop Conference Ep 094: Concrete Composition - Functional Design in Clojure "Birdsong as code" by Chris Ford (Strange Loop 2023) - Strange Loop Conference Flutter/MX In Action: A Text-to-Speech Dashboard RFE - Ken Tilton Great Clojure Software Programs -- 2023 - Clojure Diary Blogs, articles, and projects Introducing Rama's Clojure API: build end-to-end scalable backends in 100x less code - Red Planet Labs Babashka is a great Clojure entry point - Matthew Twomey ImageMagick + Pango + Babashka = ♥ - Peter Strömberg Libraries and Tools New releases and tools this week: uix 1.0.1 - Idiomatic ClojureScript interface to modern React.js tools.build 0.9.6 - Clojure builds as Clojure programs deps-new 0.5.3 - A new, simpler alternative to clj-new mina 0.1.23 - Helidon/Nima ring adapter - using loom/java21+ lingo 1.0.2 - spec explain improved spandex 0.8.2 - Elasticsearch client for Clojure (built on new ES 8.x java client) honeysql 2.4.1078 - Turn Cloju

## Hooks, Dependencies and Stale Closures

DevFeed: [Hooks, Dependencies and Stale Closures](<https://devfeed.tech/articles/hooks-dependencies-and-stale-closures-48193.md>)

Original publisher: [Read original article](<https://tkdodo.eu/blog/hooks-dependencies-and-stale-closures>)

Published: 2022-04-24T00:00:00Z

Content type: article

Language: en

Sources: [TkDodo](<https://devfeed.tech/sources/tkdodo-s-blog.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Closure](<https://devfeed.tech/topics/closure.md>), [hooks](<https://devfeed.tech/topics/hooks.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [ESLint](<https://devfeed.tech/topics/eslint.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [closure](<https://devfeed.tech/tags/closure.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [eslint](<https://devfeed.tech/tags/eslint.md>), [hooks](<https://devfeed.tech/tags/hooks.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lint](<https://devfeed.tech/tags/lint.md>), [react](<https://devfeed.tech/tags/react.md>), [react-hooks](<https://devfeed.tech/tags/react-hooks.md>)

### AI overview

This article explains how JavaScript closures interact with React hooks and dependencies, focusing on stale closures, their subtle runtime behavior, and how the react-hooks/exhaustive-deps ESLint rule can detect related issues statically.

### Source excerpt

Let's demystify what stale closures are in combination with react hooks with the help of the analogy of taking a photo ...

## What is new in Nx 13.10?

DevFeed: [What is new in Nx 13.10?](<https://devfeed.tech/articles/what-is-new-in-nx-13-10-21459.md>)

Original publisher: [Read original article](<https://nx.dev/blog/what-is-new-in-nx-13-10>)

Author: Juri Strumpflohner

Published: 2022-04-08T00:00:00Z

Content type: release

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [npm-workspaces](<https://devfeed.tech/topics/npm-workspaces.md>), [nx-cloud](<https://devfeed.tech/topics/nx-cloud.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [React](<https://devfeed.tech/topics/react.md>), [lint](<https://devfeed.tech/topics/lint.md>)

Tags: [nx](<https://devfeed.tech/tags/nx.md>), [package](<https://devfeed.tech/tags/package.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

Nx 13.10 consolidates core and CLI functionality into a single package, reducing the packages needed in an Nx workspace. It also starts the Nx Daemon automatically: the daemon watches for file changes and recomputes and caches the project graph in the background, so operations that need the graph can use it without waiting for a fresh calculation. During setup of a new Nx workspace, opting into Nx Cloud is now selected by default. The supplied excerpt ends during its discussion of Nx's plugin architecture.

### Source excerpt

Nx 13.10 brings core package consolidation, Nx Daemon by default, local plugin development, enhanced visualization, new lint rules, and React 18 support.

## Automatically format and lint code with pre-commit

DevFeed: [Automatically format and lint code with pre-commit](<https://devfeed.tech/articles/automatically-format-and-lint-code-with-pre-commit-47345.md>)

Original publisher: [Read original article](<https://interrupt.memfault.com/blog/pre-commit>)

Author: Noah Pendleton

Published: 2021-10-27T00:00:00Z

Content type: tutorial

Language: en

Sources: [Interrupt](<https://devfeed.tech/sources/interrupt.md>)

Topics: [pre-commit](<https://devfeed.tech/topics/pre-commit.md>), [Embedded Software Dev](<https://devfeed.tech/topics/embedded-software-dev.md>), [formatting](<https://devfeed.tech/topics/formatting.md>), [lint](<https://devfeed.tech/topics/lint.md>), [C](<https://devfeed.tech/topics/c.md>), [hooks](<https://devfeed.tech/topics/hooks.md>), [Git](<https://devfeed.tech/topics/git.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [also](<https://devfeed.tech/tags/also.md>), [bug](<https://devfeed.tech/tags/bug.md>), [c](<https://devfeed.tech/tags/c.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [format](<https://devfeed.tech/tags/format.md>), [hooks](<https://devfeed.tech/tags/hooks.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lint](<https://devfeed.tech/tags/lint.md>), [linux](<https://devfeed.tech/tags/linux.md>), [pre-commit](<https://devfeed.tech/tags/pre-commit.md>)

### AI overview

A tutorial on using pre-commit and Git hooks to automatically format and lint C-language firmware codebases. It explains formatting and linting, gives general guidelines and example checks, and describes benefits such as reducing style-related churn in pull request reviews.

### Source excerpt

This article provides some background and guidelines for using pre-commit to automatically format and lint C-language firmware codebases. We'll cover general guidelines and go over an example set of checks that can be helpful when working on firmware code. Continue reading...

[Next page](<https://devfeed.tech/topics/lint.md?cursor=WyIyMDIxLTEwLTI3VDAwOjAwOjAwKzAwOjAwIiwgIjVmZDg2M2Y1LTY1YjYtNGFkZC04ODc3LThjZGUwMWZlN2VmYiJd>)