Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE] Link claude hooks to documented custom autocmd events

Open
  • Is something wrong?
#216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua, neovim
Domain
developer-experience, tooling

Research direction

No files or tests are named. Start by reviewing the documented custom autocmd events and Claude Code hook configuration, then determine how the proposed :ClaudeCodeInstallAutoCmdHooks command should handle local-directory and global settings. Done means the command can help install hooks that trigger Neovim autocmds when Claude responds, including the checktime use case.

Written by the indexing model from the issue text.

Description

Feature Description

I would like the plugin to have a command to help create Claude Code hooks that will trigger auto commands on NeoVim.

Use Case

For Example, it would be useful to trigger "checktime" every time Claude responds, so the editor can check whether open buffers have been changed

Proposed Solution

Thinking out loud, :ClaudeCodeInstallAutoCmdHooks would kick off a session to help install such hooks in the local directory or global settings configuration

Alternatives Considered

I currently use a combination of TextChangedT and timer to trigger :checktime whenever changed stopped changing for over one second

Dominant language
Lua
Stars
3.1k
Forks
219
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/claudecode.nvim

All issues in coder/claudecode.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.