← all publishers

werf

@werf source repo

Report this profile Claim this profile

• 8 skills
• 0 followers
• 16 hours ago last updated

1. ▌
   Agent Code Review · werf

   Adversarial verification layer for reviewing agent-generated or otherwise untrusted implementations. Use when the author of a diff, patch, commit, or test suite is an agent, when a change touches tests or verification infrastructure, or when invoked as /agent-code-review. Adds test falsifiability checks and check-gaming detection on top of ordinary review; does not replace it.
   0
   installs
2. ▌
   Review · werf

   Code review of a pull request, branch, or diff. Covers technical, product, and risk perspectives in one pass and produces a consolidated report. Use when asked to review a PR, branch, or code changes.
   0
   installs
3. ▌
   Pull Request · werf

   Generates Pull Request titles and descriptions according to werf conventions. Use when creating or updating a PR.
   0
   installs
4. ▌
   Session Retro · werf

   Analyze the current session for harness-worthy lessons — repeated corrections, discovered conventions, skill bugs — and turn them into concrete repo changes: docs, skills, task targets, linter rules, CI checks. Use at the end of a session, when asked to reflect/retro, or when invoked as /session-retro.
   0
   installs
5. ▌
   Test The Tests · werf

   Verify a test actually falsifies the behavior it claims to cover, via real mutation. Use right after writing or changing a test, when auditing an existing suite's real coverage, or as a step inside a code review.
   0
   installs
6. ▌
   Git Conventions · werf

   werf conventions for branch names and commit messages. Use when creating a branch for a new task or committing staged changes.
   0
   installs
7. ▌
   Challenge Review · werf

   Independent challenge pass for a non-trivial or high-risk change. Use for a fresh second opinion, when a change touches tests or verification infrastructure, or when invoked as /challenge-review. Attempts to disprove implementation claims through contract recovery, test falsification, and check-gaming detection; complements ordinary review.
   0
   installs
8. ▌
   Inherited Claims · werf

   How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans. Use whenever a task starts from context you did not derive yourself, or resumes work described by a previous session.
   0
   installs