Lightweight self-hosted Git service with issues, pull requests and CI.
Beav is scouting… reading your request and matching it against the catalogue.
Beav is scouting… reading your request and matching it against the catalogue.
27 tools
Lightweight self-hosted Git service with issues, pull requests and CI.
Comparing 1
ClearUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.
Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints.
Structures git workflow practices.
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match w…
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Conducts multi-axis code review.
Use this skill when the user wants to make a Git commit or split changes into more than one commit.
Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model.
Generate a comprehensive repository summary and narrative story from commit history
Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors.
Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI).
Write a Conventional Commits message compressed to intent only.
Perform code reviews following Sentry engineering practices.
Implement the result of /to-spec and /to-tickets in code.
Use when writing a PR body.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements