pr-creation

To create a high-quality pull request for freenet-core, follow a structured workflow that enforces conventional commits, rigorous testing, regression checks, and documentation to ensure maintainable changes.

The best way to review code for a Freenet pull request is using a four-agent workflow featuring code-first, testing, skeptical, and big-picture subagents to thoroughly evaluate defects and integration safety.

Yes, you need conventional commits for your freenet-stdlib pull request to meet the enforced commit standards, which speed up safe integration and ensure maintainable repository changes.

The four-agent review workflow improves code quality by running parallel subagents that evaluate code logic, testing coverage, skeptical edge cases, and big-picture architecture to reduce defects before integration.

Yes, you can use these PR guidelines for related Freenet repositories, as the workflow applies to freenet-core, freenet-stdlib, and associated projects to reduce defects and avoid conflicts.

Required testing standards before submitting a Freenet pull request include rigorous testing, regression prevention checks, and documentation requirements to ensure safe integration and maintainable changes.