We split this skill into the rules it gives an agent

13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈11

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Run a Greptile review from the local checkout and summarize the findings.

   line 16
2. Distinctive:

   Start from the current repository root:

   line 22
3. Distinctive:

   If the command fails, tell the user that the Greptile CLI review must be run from a git repository.

   line 28
4. Very specific:

   Check whether greptile is installed:

   line 32
5. Distinctive:

   If it is missing, do not install it automatically.

   line 38
6. Distinctive:

   If npm is unavailable, offer the shell installer fallback:

   line 44
7. Very specific:

   After installation, re-run command -v greptile.

   line 50
8. Distinctive:

   Check the signed-in account:

   line 54
9. Distinctive:

   If the CLI reports that authentication is missing, run:

   line 60
10. Distinctive:

    Wait for the user to complete the login flow before continuing.

    line 66
11. Distinctive:

    If JSON output is unsupported or fails with a usage error, fall back to:

    line 76
12. Distinctive:

    Do not hide the raw command failure if both commands fail.

    line 82
13. Distinctive:

    When output is plain text, preserve the same structure as much as possible.

    line 94

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.