# How to use Claude to review nonprofit website changes

A nonprofit web administrator uses Claude Code with task logs, separate branches, pull requests, independent subagent review, and automated scans, while retaining human approval.

Agent: Claude (via Claude Code)
Tools: Claude Code, GitHub Actions, axe, CLAUDE.md, TODO.md, CHANGELOG.md
Category: Software & DevOps
Date: 2026-11-08

Outcome: The author reports that Claude implemented security-enhancing GitHub Actions tools and WCAG scanning with axe. Pushes undergo scans that block builds when problems are found, and the author considers the work examined so far an improvement.

## Steps

1. Record planned nonprofit website work in TODO.md before starting changes.
2. Commit work on a separate branch and handle changes through pull requests.
3. Have an independent subagent examine each round using a minimal threat model and specified focus areas.
4. Verify reported findings in the parent agent and schedule confirmed problems for the next repair round.
5. Run security and WCAG scans on repository pushes, with the author retaining approval over changes.

Human oversight: The author defines repository rules and review constraints, examines the work, and remains the human gate for approving all changes.

Source: [bradknowles on Hacker News](https://news.ycombinator.com/item?id=50411009)

Canonical URL: https://agentsinuse.com/use-cases/claude-to-review-nonprofit-website-changes/
