verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
agentic-commits
Commit format that AI agents can act on. Splits changes into atomic hunks, commits with structured format enabling Resume, Review, and Handoff. Never pushes.
differential-review
Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.
github-issue-updater
Link development to GitHub issues, post commit updates, and close issues on completion.
conventional-commits
Generate granular conventional commits from staged changes
Git Workflow
This skill should be used when the user needs help with git operations, merge conflicts, branch management, or commit cleanup. It provides advanced git workflow management including branching strategies, merge conflict resolution, interactive rebase guidance, and commit hygiene.
1natsu — Conventional Commits Reference
An internal reference that is automatically consulted when you need the Conventional Commits format, types, scopes, breaking-change notation, or how to write the body and footer. It is used by other skills when creating commit messages or PR titles.
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when a user wants to commit and push changes, mentions pushing to a remote, or asks to save and push their work. Also activate...
git-mcp
Git repository operations using the Git MCP server. Use when Claude needs to perform version control operations including viewing status, diffs, commit history, creating commits, managing branches, or analyzing repository changes. Triggers on requests involving git operations, version control, commit history, branch management, or repository analysis within the project.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
changelog-automation
Automate changelog generation from commits, PRs, and releases following the Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
semantic-release
Automate versioning and release notes from conventional commits
Workflow Patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
prepare-pr
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /reviewpr. Never merge or push to main.
dev-diary
Manages the automatic dev diary — a log of all commits and work sessions. The post-commit hook writes raw entries; this skill helps review, summarize, and navigate the diary. Use when asked to "show today's work", "summarize what happened", or "check the dev diary". Avoid when authoritative source-of-truth is needed for code content (use git diff/log directly for final verification).
github-docs
Investigate GitHub repositories using the gh CLI. Analyze PRs, issues, commits, CI/CD status, repo health, contributor activity, security vulnerabilities, and fetch repo docs/content. Use for any GitHub-related investigation or documentation retrieval.
pr-review
Use FIRST for any PR/code review work — checking feedback, reading CR comments, responding to reviewers, addressing review bot or human comments, or preparing commits on a PR. Collects feedback from ALL sources (conversation, inline, reviews) to prevent the common failure of missing inline feedback. Start with check-pr-feedback.sh, then reply inline where needed and summarize with one Fix Report.
market-context
Use when validating market timing, structural forces, or distribution moats before committing strategic resources—focuses on macro context, not individual competitor teardowns.
raise-pr
Create pull requests with intelligent branch names and descriptions by analyzing git changes. This skill should be used when raising PRs, creating pull requests, pushing changes, committing code, reviewing staged changes, or submitting code for review. Automatically infers meaningful branch names and PR titles from git diffs.
code-review
Review code changes via local diff, branch diff, or latest commit with severity-ranked findings and concrete fixes.
replit-policy-guardrails
Implement Replit lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Replit integrations, implementing pre-commit hooks, or configuring CI policy checks for Replit best practices. Trigger with phrases like 'replit policy', 'replit lint', 'replit guardrails', 'replit best practices check', 'replit eslint'.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
internal-audit-planning
Internal audit planning engine that builds risk-based audit universes, prioritizes engagements, designs control testing programs, and produces audit committee-ready reports. USE THIS SKILL when the user mentions internal audit plan, audit universe, control testing, audit program, audit committee reporting, audit risk assessment, sampling methodology, audit findings, issue tracking, or quality assurance and improvement program (QAIP). Covers the full audit lifecycle from planning through follow-up.
commit-creator
Generate semantic commit messages following the Conventional Commits format. Use when committing code, staging changes, writing commit messages, requesting git commit, or when the user mentions commit, commit message, conventional commits, semantic commits, git commit, stage changes, or create commit. Supports monorepo package version tracking.
conventional-commits-compliance
Agent capable of analyzing source code changes and crafting professional commit messages that adhere to the Conventional Commits 1.0.0 specification.
GitHub Sync
GitHub code sync - automatically synchronize watched GitHub open-source projects to local storage daily. Supports multiple project configurations, automatically determines whether to perform an initial clone or an incremental pull, records new commits and pushes a summary to Discord/Telegram. Suitable for scenarios like 'mirroring open-source code' and 'tracking upstream updates'. Triggered daily at 23:00 by a scheduler and can also be invoked manually.
gauntlet-commit
Gates commits behind optional gauntlet validation by detecting changes, running selected validations, handling failures, and completing the commit flow. Activates when requests include "commit with gauntlet", "run checks before commit", "run gauntlet then commit", or "skip gauntlet and commit".
validate-all
Run all project validation checks (markdown, JSON, shell scripts). Use when the user asks to "validate everything", "run all checks", or before committing changes.
pr-tldr
PR TLDR context brief — serves dual purpose: 1. **Committed state (template):** Contains the document skeleton with {{FILL}} markers. The pr-review orchestrator loads this at startup, fills in the markers during Phase 1.5, and overwrites this file with the filled result. 2. **Runtime state (filled):** After the orchestrator writes, subagent reviewers load this file and get the filled context brief. If you're reading this and see {{FILL}} markers, the template has not been filled in — either the orchestrator hasn't run yet, or you're viewing the committed source.
fresh-eyes-review
Use when about to commit, create a PR, or declare work complete — after verification-before-completion confirms tests pass but before code ships. Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.
autonomous-tests
Run autonomous E2E tests. Args: staged | unstaged | N (last N commits) | working-tree (default: working-tree with smart doc analysis). Example: /autonomous-tests 3
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when a user wants to commit and push changes, mentions pushing to a remote, or asks to save and push their work. Also activates when a user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
commit
Agent Skill for safely handling the git commit process. Use whenever the user asks to create commits
Team Collaboration Standup Notes
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
commit
Creates commits with proper conventional commit format and issue references. Use when committing code changes, creating a git commit, or saving changes.
initialize-git-repository
Set up a new Git repository and make the first commit for version control
git-commit-message
Use when about to write a git commit message, before running git commit — applies when staged changes are ready and a message needs to be drafted
LobeHub - Empowering your AI dreams
Lobe Chat - open-source, modern-design LLMs/AI chat framework. Supports OpenAI / Claude 3 / Gemini / Perplexity / Bedrock / Azure / Mistral / Ollama, Multi-Modals (Vision/TTS) and plugin system.
git-stats
Analyze any git repository for contributor stats, code frequency, language breakdown, file hotspots, and commit trends.
release-notes
Analyzes git commit and PR history to generate structured release notes (RELEASE_NOTES.md). Automatically categorizes changes, identifies contributors, and produces a polished release document through a brief confirmation interview.
Varlock Claude Skill
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits
mp-commit
Stage and commit changes with conventional commit format. Use when: "commit this", "stage and commit", "make a commit"