ar-taskflow-review

Reviews branch diffs against project coding rules and tracks review iterations.

1|2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-taskflow-review-mahsanamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ar-taskflow-review
Source: https://github.com/mahsanamin/agentic-repos/tree/main/skills/ar-taskflow-review
Command: npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-taskflow-review-mahsanamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often drift from a team's established conventions, and manual review against every coding rule is slow and inconsistent. This Skill automates standards-based review by diffing the current branch against the base branch and validating every change against the project's coding rules. ## Core Features & Use Cases - Rule-based diff analysis: Generates a diff of the current branch versus main (including uncommitted changes) and checks it against all coding standards files, citing file:line and the specific rule violated. - Iteration tracking: Appends timestamped review iterations to a git-ignored review report, recording which issues were fixed and which are new across re-reviews. - Workflow integration: Detects whether it runs inside the ar-taskflow workflow or standalone, and resolves a project-specific code-reviewer agent with a generic fallback. - Use Case: After implementing a feature on a branch, run the review to catch N+1 queries, missing migrations, or transaction-scope violations before opening a pull request. ## Quick Start Ask the assistant to run ar-taskflow-review on the current branch to validate the changes against the project coding rules.

Frequently Asked Questions about ar-taskflow-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes against project coding standards?▼

Run ar-taskflow-review on your current branch. It generates a diff against the base branch, loads all coding rules from the configured standards directory, and produces a report with passes, warnings, blocking issues, and suggestions citing file:line and the violated rule.

How to track code review progress across multiple iterations?▼

Each run appends a timestamped iteration to review-report.md in a git-ignored reviews directory. Re-reviews read previous iterations, note which issues were fixed, and flag any new issues introduced.

Does the review include uncommitted working tree changes?▼

Yes. The diff runs from the merge-base to the working tree, so it captures both committed and uncommitted changes in one pass, and reports the diff type accordingly.

Will running a code review modify or commit files in my repo?▼

No tracked files are modified. Review artifacts are written only to the git-ignored reviews_root or .claude/reviews fallback directory, which is added to .gitignore at install time.

What happens if no project-specific reviewer agent is installed?▼

The skill searches for an installed project-specific *-code-reviewer agent first. If none exists, it falls back to the generic a_sag_code_reviewer agent, which applies the coding rules from the standards directory.

Should I amend commits after addressing review feedback?▼

No. Post-review fixes must go into a new commit with a normal push. The skill explicitly forbids git commit --amend and force pushes for post-review changes.