claude-skills

A curated collection of skills for Claude Code.

Install

Copy skill files from .claude/commands/ into one of these locations:

• Repo-local: $REPO_ROOT/.claude/commands/<skill-name>.md
• User-global: $HOME/.claude/commands/<skill-name>.md

Skills

conventional-commits

Creates and refines commit messages that comply with Conventional Commits v1.0.0.

Triggering requests:

• Requests to create a commit.
• Requests to write or edit a commit message.
• Requests to run git commit.

Core behavior:

• Run pre-commit safety checks: abort if staged files match blocked patterns (secrets, databases, dependencies, build output, cache, OS noise, logs) or if diff content contains secret patterns (private keys, AWS keys, credential assignments).
• Enforce Conventional Commits header format: <type>[optional scope][!]: <description>.
• Require BREAKING CHANGE: footers when applicable.
• Create the commit after all checks pass, then push the current branch.
• If Git LFS is configured, push branch-reachable LFS objects before the final branch push.

forgejo-workflows

Creates, updates, and troubleshoots Forgejo Actions workflow files for CI/CD pipelines.

Triggering requests:

• Requests explicitly about Forgejo workflows or Forgejo actions.
• If a request says only "workflow" or "actions", ask whether the user means GitHub or Forgejo before proceeding.

Core behavior:

• Write workflow files under .forgejo/workflows/.
• Use https://forgejo.org/docs/next/user/actions/reference/ as the syntax and behavior reference.
• Use https://code.neureka.dev/api/v1/repos/search?team_id=3&sort=alpha&limit=1000 to discover valid actions.
• Build action identifiers from JSON as {owner.login}/{name}, then use uses: as {owner.login}/{name}@{ref} (example: actions/docker-build-push@v6).
• For tag-based action refs, pin to major version if possible, then major.minor, then the latest version tag; use latest only as fallback.
• Always use runs-on: ubuntu-latest.
• Use https://code.neureka.dev/api/v1/repos/<owner>/<name>/tags (example: /api/v1/repos/actions/docker-build-push/tags) to validate tag-based action refs.