Agent skill

Lint Commit PR

by Tresjs in Tresjs/tres

Lint local changes, auto-fix, conventional commit, and optionally create PR

MITAuto-check passedDevelopment

Install Lint Commit PR

skills CLI
$ npx skills add Tresjs/tres --skill lint-commit-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Tresjs/tres lint-commit-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Tresjs/tres.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/lint-commit-pr .claude/skills/lint-commit-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lint-commit-pr
GitHub stars
3.8k
Token cost
~1.1k tokens
SKILL.md length
472 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Lint local changes, auto-fix, conventional commit, and optionally create PR

  • Works in 11 steps: Handle pr-only mode (if specified) → Check git status to identify modified… → Run linter with auto-fix on affected… → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers Steps, Examples, Commit Message Examples and Considerations
  • Calls git, gh and pnpm

What it does

Lint Commit PR is an agent skill from Tresjs/tres. Lint local changes, auto-fix, conventional commit, and optionally create PR

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Linting and formatting, Commit messages and Pull requests. It works with Vite, Vue.js, Three.js and Git. The repository describes itself as: Declarative ThreeJS using Vue Components. The licence is MIT.

When your agent uses it

  • Tasks that involve Linting and formatting
  • Tasks that involve Commit messages
  • Tasks that involve Pull requests

Example prompts

  • “/lint-commit-pr”

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Handle pr-only mode (if specified)
  2. Check git status to identify modified files and ensure there are changes to commit
  3. Run linter with auto-fix on affected projects only
  4. Verify lint passed - if there are remaining lint errors that couldn't be auto-fixed, report them and stop
  5. Stage all changes using git add -A to ensure all modifications (including lint fixes) are staged
  6. Analyze the changes
  7. Generate conventional commit message following this format
  8. Show the commit message to the user and ask for confirmation
  9. Commit the staged changes with the approved message
  10. Push to remote using git push -u origin HEAD
  11. Handle PR creation based on parameter

What it can do on your machine

Read from SKILL.md and the folder at commit 443197b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh and pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lint Commit PR loads about 1.1k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 472 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Tresjs/tres at commit 443197b, republished under its MIT licence (© Tresjs). 472 words, ~1,090 tokens.

Download SKILL.mdSave it as .claude/skills/lint-commit-pr/SKILL.md (or your agent's skills folder).
name
lint-commit-pr
description
Lint local changes, auto-fix, conventional commit, and optionally create PR

Lint, Commit and Create PR

Lint local changes, auto-fix issues, generate conventional commit message based on monorepo changes, and optionally create a PR.

Parameters: $ARGUMENTS

  • pr - Force create PR even if one exists
  • no-pr - Skip PR creation, only commit and push
  • pr-only - Only create/update PR, skip lint and commit steps
  • If no parameter provided, auto-detect if PR exists

Steps

  1. Handle pr-only mode (if specified):

    • Skip to step 11 (PR creation/update)
    • Use existing commits for PR description
  2. Check git status to identify modified files and ensure there are changes to commit

  3. Run linter with auto-fix on affected projects only:

    • Run pnpm nx affected -t lint --fix to lint only projects with changes
    • This uses NX's affected graph to skip unchanged projects
  4. Verify lint passed - if there are remaining lint errors that couldn't be auto-fixed, report them and stop

  5. Stage all changes using git add -A to ensure all modifications (including lint fixes) are staged

  6. Analyze the changes:

    • Use git diff --staged to review all staged modifications
    • Identify which workspace(s) were affected (packages/, apps/, tools/*)
    • Determine the type of change (feat, fix, chore, docs, refactor, test, style, perf)
  7. Generate conventional commit message following this format:

    • <type>(<scope>): <description> where scope is the package/app name
    • Examples:
      • fix(core): resolve memory leak in dispose method
      • feat(cientos): add new OrbitControls component
      • docs(playground): update examples with new API
      • chore(docs): update navigation structure
    • If changes span multiple packages, use the primary affected package or use monorepo
    • Keep description concise and in imperative mood
  8. Show the commit message to the user and ask for confirmation

  9. Commit the staged changes with the approved message

  10. Push to remote using git push -u origin HEAD

  11. Handle PR creation based on parameter:

    • If no-pr parameter: Stop here, changes are pushed
    • Otherwise, check if PR exists using gh pr view (will fail if no PR exists)
    • If PR exists and no pr parameter: Skip PR creation, inform user PR will auto-update
    • If no PR exists OR pr parameter provided: Create PR using gh pr create with:
      • Title: same as commit message (or summarize recent commits if pr-only mode)
      • Body: A structured summary including:
        • Summary: bullet points of what changed

        • Changes: list of modified files/areas

        • Test plan: how to verify the changes work

Show full SKILL.md (94 more words)Show less

Examples

bash
# Auto-detect (default behavior)
/lint-commit-pr
# Lints, commits, pushes
# Checks if PR exists with: gh pr view
# If PR exists: "✓ Changes pushed. Existing PR will update automatically"
# If no PR: Creates new PR

# Skip PR creation
/lint-commit-pr no-pr

# Force create PR
/lint-commit-pr pr

# Update existing PR only (skip lint/commit)
/lint-commit-pr pr-only

Commit Message Examples

# Single package fix
packages/core/src/useRenderer.ts modified
→ fix(core): prevent renderer disposal on component unmount

# Feature in cientos
packages/cientos/src/components/Stars.vue added
→ feat(cientos): add Stars component for particle effects

# Documentation update
apps/docs/content/guide/getting-started.md modified
→ docs(docs): clarify installation instructions

# Multiple packages
packages/core and packages/cientos modified
→ feat(monorepo): add shared composable for camera controls

Considerations

  • Always run pnpm nx affected -t lint --fix before committing
  • Never commit if there are unfixable lint errors
  • Use conventional commit types: feat, fix, chore, docs, refactor, test, style, perf, ci
  • Scope should match package/app name from package.json (e.g., core, cientos, docs)
  • Commit description: concise, imperative mood, lowercase
  • Always ask for user confirmation before committing and pushing
  • Use -u flag for first-time pushes
  • Use gh pr view to check if PR exists (exit code 0 = exists)
  • If PR exists, inform: "✓ Changes pushed. Existing PR #{number} will update automatically: {url}"

© Tresjs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/lint-commit-pr of Tresjs/tres.

Open the folder on GitHubat commit 443197b

Compare with similar skills

Lint Commit PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lint Commit PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lint Commit PR this skillTresjs/tres3.8k—~1.1kAutomated safety check: PassMIT
PR Pushicebear0828/codex-proxy1.8k—~2.2kAutomated safety check: NotesCustom licence
PR Pushicebear0828/codex-proxy1.8k—~2.3kAutomated safety check: NotesCustom licence
Git Commitpddzl/td27-admin112—~147Automated safety check: PassMIT
Git PR Workflowandymai/brepjs114—~2.9kAutomated safety check: PassApache-2.0
Development Workflowkid-sid/claude-spellbook189—~3.2kAutomated safety check: PassMIT

Similar skills

  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check: notes
  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check: notes
  • Git Commit

    pddzl/td27-admin

    Generate clear and conventional commit messages from git diffs

    112 GitHub stars~147 tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Git PR Workflow

    andymai/brepjs

    This skill should be used when committing, pushing, branching, or merging in the brepjs repository — when a task involves "pre-commit hook failed" (which tier ran, how to bypass), "commit rejected…

    114 GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Development Workflow

    kid-sid/claude-spellbook

    A skill your agent uses when choosing a branching strategy, writing a commit message, opening or reviewing a pull request, setting up commit linting, or tagging a versioned release.

    189 GitHub stars~3.2k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

More from Tresjs/tres

  • New Experiment

    Tresjs/tres

    Create a new experiment in TresJS Lab with all necessary files

    3.8k GitHub stars~782 tokensUpdated today
    Auto-check passed

Categories

Questions about Lint Commit PR

What does Lint Commit PR do?

Lint local changes, auto-fix, conventional commit, and optionally create PR. Lint Commit PR is an agent skill from Tresjs/tres.

When should I use Lint Commit PR?

Lint Commit PR fits situations like: tasks that involve Linting and formatting; tasks that involve Commit messages; tasks that involve Pull requests.

How do I install Lint Commit PR in Claude Code?

Run `npx skills add Tresjs/tres --skill lint-commit-pr -a claude-code`. Or copy the skill folder (.agents/skills/lint-commit-pr in Tresjs/tres) into .claude/skills/lint-commit-pr in your project. Claude Code loads it when a task matches its description.

How do I install Lint Commit PR in Codex?

Run `npx skills add Tresjs/tres --skill lint-commit-pr -a codex`. Or copy the skill folder (.agents/skills/lint-commit-pr in Tresjs/tres) into .agents/skills/lint-commit-pr in your project. Codex loads it when a task matches its description.

Can I use Lint Commit PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Tresjs/tres --skill lint-commit-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lint-commit-pr, .gemini/skills/lint-commit-pr, .github/skills/lint-commit-pr and .opencode/skills/lint-commit-pr in your project.

What does Lint Commit PR need to run?

Going by SKILL.md and its folder, Lint Commit PR needs the command-line tools its instructions call (git, gh and pnpm).

Does Lint Commit PR access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Lint Commit PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lint Commit PR use?

Lint Commit PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lint Commit PR use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lint Commit PR?

Skills that share tags, products or a category with Lint Commit PR: PR Push (icebear0828/codex-proxy, 1.8k stars), PR Push (icebear0828/codex-proxy, 1.8k stars), Git Commit (pddzl/td27-admin, 112 stars) and Git PR Workflow (andymai/brepjs, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lint Commit PR?

Tresjs (a GitHub organization) maintains it in Tresjs/tres, which has 3,753 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

Source: Tresjs/tres on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.