skills.rest
marin-community
marin-communityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lint-review

Runs the infra/lint catalog review on a pull request and posts findings as inline GitHub comments.

3.2k|266|Updated Mar 22, 2024
Search Tags:#static analysis#lint#ci#inline comments#gitHub#Code review#Pull request
One-click install
npx skills add https://github.com/marin-community/marin --skill lint-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint-review
Source: https://github.com/marin-community/marin/tree/main/.agents/skills/lint-review
Command: npx skills add https://github.com/marin-community/marin --skill lint-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates running the Marin infra/lint catalog review over a pull request's branch diff and reporting every finding on the PR, removing the manual work of executing the linter and transcribing results into review comments.

Core Features & Use Cases

  • Automated lint review execution: Runs ./infra/pre-commit.py --review against the PR branch diff versus the merge base with origin/main, covering committed and uncommitted work.
  • Faithful finding reporting: Posts each finding verbatim as an inline review comment at its file and line, with a single fallback issue comment for findings that anchor outside the PR diff.
  • Idempotency guard: Detects the <!-- marin-lint-review --> marker in existing comments to avoid duplicate lint passes on the same PR.
  • Use Case: In CI, after checking out a PR head and fetching origin/main, invoke this skill to run the lint catalog review and surface all findings as inline comments without editing or committing anything.

Quick Start

Run the lint review on pull request 123 and post the findings as inline comments.

Frequently Asked Questions about lint-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the lint review on a pull request?▼

Run ./infra/pre-commit.py --review from the repo root with MARIN_REVIEW_TRIGGER, MARIN_REVIEW_PR_NUMBER, and MARIN_REVIEW_HEAD_SHA set. The command reviews the branch diff against the merge base with origin/main and prints findings in path:line format.

How are lint findings posted to a GitHub pull request?▼

Each finding is posted as one inline review comment at its file and line using the inline comment tool, with the message copied verbatim. Findings on lines outside the PR diff are collected into a single fallback issue comment via gh pr comment.

Can this skill fix or commit the lint issues it finds?▼

No. The skill is strictly read-only except for posting comments. It never edits, stages, commits, pushes, or runs state-changing git or gh commands; it only runs the review and reports findings faithfully.

What happens if the lint review finds no issues?▼

If the command exits zero with no findings, nothing is posted to the PR. The green CI job check itself signals a clean lint pass, and the skill simply states that there are no findings.

Why did the lint review fail to run on my PR?▼

A failed run means the command exited non-zero, every review lane failed, the agent command was not found, or the merge base with origin/main could not be resolved. This is reported as a failure in the job log, not posted as a PR comment.

Related Skills

Explore More Software Engineering Skills→
jamescjamesc

resolve-merge

Merge origin/main into the current branch and resolve conflicts.

Community
Advanced
PandelisZPandelisZ
1

babysit

Triage pull request comments, resolve conflicts, and fix CI until merge-ready.

Community
Intermediate
secondskysecondsky
204

woocommerce-dev-cycle

Run PHP and JavaScript tests, linting, and quality checks in WooCommerce projects.

Community
Intermediate
CaltexBevoCaltexBevo

qa-only

Run report-only QA tests on web applications and generate structured bug reports.

Community
Intermediate