necturalabs

Create, audit, shrink or restructure an AGENTS.md instruction file. Use when writing a repository's AGENTS.md, auditing one for stale or oversized guidance, deciding what belongs in persistent instructions versus a skill, a document or a lint rule, or migrating instruction files between agent harnesses. Not for editing ordinary project documentation.

Independently review a finished non-trivial code change for correctness, design, compatibility and test gaps before it is committed or merged. Use when a behavioral, cross-file, schema, dependency or concurrency diff is complete and needs a reviewer that did not write it. Not for a typo, a formatting-only diff, or code that is still being written.

Assess a change for security defects when it touches authentication, authorization, sessions, tokens, cryptography, secrets, external input, deserialization, file or network boundaries, permissions, or dependencies. Use before the general code review on such changes. Not for changes with no threat surface, and not for generic code-quality review.

Write, repair, debug, audit or delete automated tests. Use when adding coverage for new behavior, writing a regression test for a defect, fixing a failing or flaky test, choosing the right test level, or auditing a suite's quality. Not for explaining what an existing test does, and not for running a suite as a routine verification step.