agent-ops-versioning
Manage semantic versioning, changelog generation, and release notes. Auto-generates entries from completed issues or git diff.
Browse published AI skills maintained by weholt. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
110Repository stars across indexed skills
32Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Manage semantic versioning, changelog generation, and release notes. Auto-generates entries from completed issues or git diff.
Create/update .agent/constitution.md. Use when commands/boundaries/constraints must be confirmed before baseline or code changes. Draft v0 from repo evidence, then interview user.
Extract, plan, or propose implementation details at configurable depth levels (low/normal/extensive). Outputs to reference files for team discussion and handoff.
Interactive code review for agent iterations. Captures comments, tracks resolution status, and integrates with git diffs.
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
Deep, excruciating code review. Use anytime to analyze code for correctness, edge cases, security, performance, and design issues. Not tied to baseline—this is pure code analysis.
Dogfooding discovery agent — establish human-approved project baseline from public docs without code inspection
Platform/Language agnostic API delivery and correctness auditor. Use when project contains API endpoints to verify contract alignment, endpoint behavior, and test coverage.
Docker image reviews, optimization, and step-building guidance. Analyzes Dockerfiles for best practices, security issues, and anti-patterns.
Handle failures and errors during workflow. Use when build breaks, tests fail unexpectedly, or agent gets stuck. Semi-automatic recovery with user confirmation for destructive actions.
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
Create .agent/baseline.md and later compare against it. Use when capturing baseline build/lint/test results or investigating newly introduced findings.
Dependency management, updates, and security advisory handling. Use when adding, updating, or auditing project dependencies.
Install AgentOps into a new or existing project. Handles .agent/ setup and .github/ merging.
Extract, plan, or propose implementation details at configurable depth levels (low/normal/extensive). Outputs to reference files for team discussion and handoff.
Interactive code review for agent iterations. Captures comments, tracks resolution status, and integrates with git diffs.
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
Handle failures and errors during workflow. Use when build breaks, tests fail unexpectedly, or agent gets stuck. Semi-automatic recovery with user confirmation for destructive actions.
Language-aware build orchestration that detects project language and runs appropriate build pipeline
Install AgentOps into a new or existing project. Handles .agent/ setup and .github/ merging.
Create/update .agent/constitution.md. Use when commands/boundaries/constraints must be confirmed before baseline or code changes. Draft v0 from repo evidence, then interview user.
Dependency management, updates, and security advisory handling. Use when adding, updating, or auditing project dependencies.
Manage semantic versioning, changelog generation, and release notes. Auto-generates entries from completed issues or git diff.
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.