github-profile

Use when the user wants Greptile to review the current local branch iteratively until all findings are resolved, before opening a PR or merging to main.

Use when asking to improve a codebase, refactor for quality, find architectural issues, audit code health, or surface improvement opportunities — DRY…

Use when a large approved body of work — a codebase audit's findings, a multi-part refactor, a long feature — must be split into tasks and driven to…

Use when the user says "let's discuss", "lets discuss", "I want to discuss", "can we discuss", "let's brainstorm", "lets brainstorm", "I want to brainstorm"…

Use when a feature or change needs an implementation plan with concrete tasks, file paths, and test steps before coding begins

Use when a plan or feature branch is ready to merge into main (e.g.

Use when comparing libraries or frameworks, evaluating approaches or architectures, investigating a technology or topic, finding best practices, deep-diving…

Use when you have a written implementation plan to execute or when given a Jira issue / ticket link to implement

Use when checking a pull request for review comments, reviewer status, CI/approval status, or resolving code review feedback.

Use when starting any new work that requires creating a git branch

Use when reviewing pull requests, PRs, code changes, or code quality.

Use when releasing a new version with semver bump (major/minor/patch) for any language project, before tagging and pushing