review-check

Review Issues Check

When working with a source file that may have been previously reviewed by Qualimetry, follow this workflow to retrieve and present any review issues found.

Step 1: Determine the Target File

Identify the file to check:

• If invoked with an argument (e.g. review-check src/MyService.cs), use that file path.
• Otherwise, use the file currently being discussed or edited in the conversation.

Step 2: Gather Repository Information

Determine the repositoryName and branchName:

repositoryName — the repository name in owner/repo-name format (e.g., organisation/my-project). The server is case-insensitive and handles .git suffixes automatically.

analysisName (optional, Qualimetry Enterprise only) — if the repository is a mono-repo with multiple analysis projects, provide the analysis project name to disambiguate. Case-insensitive. Leave empty for single-project repositories. If omitted and multiple projects are found, the server returns an error listing the available analysis names.

branchName — run this shell command:

git branch --show-current

This returns the branch name (e.g., main, develop, feature/login-page).

pullRequest (optional) — to limit the results to the issues raised on a pull request's new code, supply the PR number. Resolve it for the current branch using standard git only — no GitHub/Azure/Bitbucket CLI required. Every major host advertises the PR as a ref whose head equals the source-branch tip, so match the branch's remote head SHA against those refs:

BRANCH=$(git branch --show-current)
SHA=$(git ls-remote origin "refs/heads/$BRANCH" | cut -f1)
git ls-remote origin "refs/pull/*/head" "refs/merge-requests/*/head" "refs/pull-requests/*/from" \
  | awk -v s="$SHA" '$1==s{print $2; exit}' | grep -oE '[0-9]+' | head -1

This covers GitHub (refs/pull/<n>/head), GitLab (refs/merge-requests/<n>/head) and Bitbucket Server (refs/pull-requests/<n>/from). If it prints nothing — the branch is not pushed, or the host does not expose PR refs over git (e.g. Bitbucket Cloud, Azure DevOps) — omit pullRequest and the tools return all review issues for the file.