werf
Official@werf
werf CI/CD tool and related projects
Agent Skills by werf
Showing 14 vetted skills indexed across 1 GitHub repositories.
werfchallenge-review
Reviews code changes adversarially by mutating implementations and detecting test-gaming patterns.
werfinherited-claims
Re-verify conclusions inherited from prior sessions against primary sources before publishing.
werfpull-request
Generates Pull Request titles and descriptions following werf conventions.
werfgit-conventions
Generates branch names and commit messages following werf repository conventions.
werftest-the-tests
Validates tests by applying real code mutations and confirming they fail as expected.
werfreview
Reviews pull requests, branches, and diffs across technical, product, and risk perspectives.
werfsession-retro
Analyze session transcripts for corrections and conventions, then convert findings into repo documentation and tooling changes.
werfgit-branch-name
Generate Werf-conform git branch names from task descriptions and type/scope.
werfreview-multi
Combine technical, product, and risk analyses into one consolidated code review report.
werfpull-request-name
Generate PR titles following werf conventions with a 72-character limit.
werfreview-product
Assess product changes for DoD alignment, user impact, and Werf/Nelm behavior.
werfreview-tech
Review Go, werf, Docker, and nelm code changes against SOLID/DRY/KISS principles.
werfreview-risk
Synthesize risks from technical and product reviews into a decision-ready table.
werfgit-commit-message
Generate Werf-style commit messages from staged git changes.
Frequently Asked Questions About werf
FAQPage SchemaWhat specific tasks are enabled by these repository management skills?▼
These skills enable standardized Git branch naming, automated pull request title generation, and structured commit message creation. Additionally, they provide comprehensive review frameworks for Go, Docker, and Nelm codebases, ensuring alignment with product requirements, technical architectural principles, and risk mitigation strategies.
Which personas benefit most from these development standards?▼
Software engineers, DevOps practitioners, and technical leads working within Git-centric environments benefit most. These skills are specifically designed for teams utilizing Nelm and Docker who require strict adherence to commit conventions and rigorous, multi-faceted code review processes to maintain high-quality, maintainable project histories.
What are the prerequisites for implementing these review and naming standards?▼
Implementation requires a Git-based version control environment and a project structure utilizing Go, Docker, or Nelm. Users must integrate these naming and review patterns into their existing development lifecycle to ensure that branch names, commit messages, and pull request titles conform to the established project conventions.