Review every file changed in a boto branch, PR, or commit range against CONTRIBUTING.md and DESIGN.md with one reviewer per file, then merge the findings into one deduplicated list sorted by severity. Use when asked for a per-file guideline/design-system review of a set of changes.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Runs workflow.py (next to this file) with run_workflow: one read-only lite child
session per changed text file, then one session that removes duplicates, drops findings
that are clearly wrong, and sorts by severity (critical → info). The final list is in
pt-BR, printed in the run output between FINAL_MARKDOWN_BEGIN and FINAL_MARKDOWN_END.
Reviewers check out HEAD from origin, so the commits must be pushed.
Constants at the top of workflow.py:
HEAD_REF (default "HEAD"): the tip to review. Check out the branch first, or set a
ref/SHA.BASE_REF (default None): None uses the merge-base with origin/develop. If the
checkout is develop itself, it uses HEAD^1 instead, which is the last merge.REPO_DIR (default /home/ubuntu/repos/boto): the local clone used to list the files.Edit the constants in a copy of the file, not in the repo (for example
cp workflow.py ~/workflows/review.py). Then pass that path as script_path.
Deleted files and binary files (images, fonts) are skipped. Each changed text file gets one reviewer. Tell the user how many files that is before starting a wide range.
git -C <REPO_DIR> fetch origin, then check out the target.run_workflow(workflow_name="review-contributing-design", script_path=<path to workflow.py>).FINAL_MARKDOWN_* markers to a .md file and
attach it for the user. Spot-check one or two findings before reporting.fazedordecodigo/boto
72c5df8
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.