Add wait skill and AI writing guard

[Miyamura80]

Summary

• add an agent-facing wait skill that issues minute-by-minute bash sleep 60 commands so CLI timeouts stay under 2 minutes
• introduce an ai writing checker (em dash detection) plus integrate it into Prek pre-commit and the linter workflow
• document the never-force-push policy in CLAUDE.md

Testing

• uv run python scripts/check_ai_writing.py

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a new /wait skill for minute-by-minute sleeping, introduces a repository-wide “AI writing” check that fails on em dashes, wires that check into pre-commit and the GitHub Actions lint workflow, and documents a never-force-push policy in CLAUDE.md.

The main functional addition is scripts/check_ai_writing.py, which walks the repo and reports em-dash occurrences. One correctness concern is that its directory skipping logic can be overly broad and skip arbitrary source directories if they share names with entries in SKIP_DIRS, creating false negatives. There’s also a minor CI robustness concern in the workflow around assumptions about where uv is installed and which PATH entry is needed.

Confidence Score: 3/5

• Safe to merge, but there are a couple of correctness/robustness nits worth addressing.
• Changes are mostly additive (docs + hook + workflow). The only code path is the new repository scanner; its current skip logic can miss files, and the workflow’s uv install PATH assumption could cause CI flakiness depending on environment.
• scripts/check_ai_writing.py, .github/workflows/linter_require_ruff.yaml

Important Files Changed

Filename	Overview
.claude/skills/wait/SKILL.md	Adds a new agent-invocable /wait skill that loops sleep 60 calls to stay under the shell timeout; no code-level issues found.
.github/workflows/linter_require_ruff.yaml	Adds an AI-writing check step to the lint workflow; potential fragility in uv installation/PATH assumptions.
.pre-commit-config.yaml	Adds a local pre-commit hook to run the AI-writing check via uv; configuration looks consistent with other always_run hooks.
CLAUDE.md	Documents a never-force-push policy in the Git workflow section; straightforward doc-only change.
scripts/check_ai_writing.py	Introduces a repository-wide em-dash detector; main concern is overly broad directory skipping that can miss files.

[greptile-apps]

_{5 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

iter_text_files() skips any file whose relative path parts contain a name in SKIP_DIRS. This will also skip user/source directories that happen to share a name with these entries (e.g., a package named cache/, node_modules/, etc.), not just the intended hidden/tooling dirs at repo root. If the intent is to skip only top-level tool directories, this will produce false negatives where em dashes in those directories are never checked.

Also appears in the same function at scripts/check_ai_writing.py:55.

Prompt To Fix With AI

This is a comment left during a code review.
Path: scripts/check_ai_writing.py
Line: 51:56

Comment:
`iter_text_files()` skips any file whose *relative path parts* contain a name in `SKIP_DIRS`. This will also skip user/source directories that happen to share a name with these entries (e.g., a package named `cache/`, `node_modules/`, etc.), not just the intended hidden/tooling dirs at repo root. If the intent is to skip only top-level tool directories, this will produce false negatives where em dashes in those directories are never checked.

Also appears in the same function at `scripts/check_ai_writing.py:55`.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Additional Comments (1)

.github/workflows/linter_require_ruff.yaml
This workflow installs uv via curl ... | sh and then hard-codes $HOME/.cargo/bin onto PATH. Depending on how uv is installed (and future changes to the installer), uv may not land in that directory, leading to intermittent "uv: command not found" CI failures. Consider using the installer’s documented install dir output (or ~/.local/bin) / verifying uv --version after install so PATH is correct.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/linter_require_ruff.yaml
Line: 24:26

Comment:
This workflow installs uv via `curl ... | sh` and then hard-codes `$HOME/.cargo/bin` onto PATH. Depending on how `uv` is installed (and future changes to the installer), `uv` may not land in that directory, leading to intermittent "uv: command not found" CI failures. Consider using the installer’s documented install dir output (or `~/.local/bin`) / verifying `uv --version` after install so PATH is correct.

How can I resolve this? If you propose a fix, please make it concise.