Agent skill · software engineering · n8n-io
n8n:human-like-code-review
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.
Why this skill is useful
Adds a complex workflow for automated, human-like code reviews with specific architectural and security considerations, producing actionable markdown feedback.
What it needs
Requires gh, git installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Human-Like Code Review Review a GitHub pull request with a code-review mindset and produce a copy/paste-friendly markdown file of feedback. Context is the foundation: understand the problem, intended solution, and surrounding architecture before judging the diff. Findings are the primary focus: prioritize architecture, over-complexity, bugs, regressions, security edge cases, and missing tests. Do not make code changes unless the user explicitly asks for them. Input The user must provide a GitHub pull request URL (e.g. https://github.com/n8n-io/n8n/pull/1234). If not provided, ask for it before proceeding. Extract the PR number and repository from the URL and use the gh CLI to fetch the PR diff and metadata. Workflow 1. Parse the PR URL to get owner, repo, and PR number. 2. Fetch the PR diff: gh pr diff <number> --repo <owner>/<repo> 3. Fetch PR metadata: gh pr view <number> --repo <owner>/<repo> 4. Fetch existing review comments: gh api repos/<owner>/<repo>/pulls/<number>/comments 5. If the PR description mentions a Linear issue, pull the ticket context with n8n:linear-issue before reviewing the diff. Use the ticket description, comments, linked GitHub issues/PRs, media, related issues, affected node popularity, and effort estimate as review context. If the skill is not available, fetch the same Linear context through the active Linear MCP or ask the user to provide the ticket details before continuing. 6. Build a short context model: what problem is being solved, what behavior is expected, which packages or systems are affected, and what constraints come from the PR description, Linear ticket, linked issues, specs, or existing code. 7. Review the diff thoroughly with a critical, code-review mindset. 8. Produce a new .md file named review-<repo>-<number>.md inside the repo's gitignored tmp/ folder, so it is never committed (the tmp folder is listed in .gitignore). Create the folder if needed (mkdir -p tmp) and write to tmp/review-<repo>-<number>.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/human-like-code-review