Review a change
Start with a local diff, read the risk signals, and give your agent line-level feedback.
After installing the skill, open the repository in your coding agent. You can inspect a local change before opening a pull request, without signing in to ArchDev.
1. Ask your agent to inspect the change
Review my current changes with ArchDev. Show me what deserves attention and why.
The agent can use archdev inspect guide for its workflow and archdev inspect to open a local diff. If no analysis is available, you can still read the diff; an absent grade is not a low grade.
2. Read the important parts first
Start with the review's risk grade and explanation, then follow any Start here list or flagged hunks. Check the relevant tests and whether they crossed the boundaries the change affects. Understand risk grades explains the difference between an overall assessment, a line-level concern, and work that has not been assessed.
3. Give feedback on the code
Select a changed line or hunk and describe the behavior you want checked or changed. Ask the agent to address it, then inspect the revised diff and rerun the affected tests. A new commit is a new revision: revisit its risk signals rather than relying on an earlier assessment.
If your team uses a shared room, the agent can use archdev log to share useful findings with teammates. That requires an ArchDev account; local code inspection does not.