mauroporras
20 verified skills60 total stars
misc-configs/claude/skills/01-commit-staged-dont-push
--- disable-model-invocation: true context: fork argument-hint: [issue-number] allowed-tools: Bash(git commit:*) model: claude-haiku-4-5 --- # Commit STAGED changes, don't push ## Context - Current staged changes only: !`git diff --staged` - Issue number argument (empty if none): `$ARGUMENTS` ## Your task Create a commit for the STAGED changes above using `git commit`. REQUIRED: - Subject line: Conventional commits format, e.g. `type(scope): description`. Prioritize brevity over gramm
tools3
misc-configs/claude/skills/00-reminder
--- disable-model-invocation: true model: claude-haiku-4-5 --- # Reminder before continuing ## Your task REMEMBER: - Run ALL Git commands from the current working directory. NEVER `cd` into other directories to run Git. Git automatically finds the repo root. Confirm you've understood the above before continuing.
data-ai3
misc-configs/claude/skills/02-opinion-staged-changes
--- disable-model-invocation: true allowed-tools: Read --- # Opinion on STAGED changes ## Context - Current staged changes only: !`git diff --staged` ## Your task Based on the above STAGED changes, provide your opinion on: - Code quality and style consistency with the existing codebase - Potential bugs, edge cases, or issues - Whether the changes are well-structured and focused - Any other suggestions for improvements ALWAYS: - Keep your feedback concise and actionable. NEVER: - Run ad
tools3
misc-configs/claude/skills/05-create-branch-staged
--- disable-model-invocation: true context: fork allowed-tools: Bash(git checkout:*) model: claude-haiku-4-5 --- # New branch for STAGED changes ## Context - Current Git diff (staged changes only): !`git diff --staged` ## Your task Based on the above STAGED changes, create a new branch with a descriptive name. ALWAYS: - Use one of the following prefixes based on the type of change: - build/some-build-change - chore/some-chore - ci/some-ci-change - docs/some-docs-update - feat/so
tools3
misc-configs/claude/skills/03-familiarize-branch-changes
--- disable-model-invocation: true allowed-tools: Read --- # Get familiar with the current branch's changes ## Context - Commits on this branch: !`git log origin/HEAD..HEAD --oneline` - List of changed files: !`git diff origin/HEAD...HEAD --stat` - Full diff: !`git diff origin/HEAD...HEAD` ## Your task Analyze the changes purely based on the code (do not check the branch name, linked GitHub issues, PR descriptions, or any other contextual clues). ALWAYS: - Provide a summary that includes:
tools3
misc-configs/claude/skills/06-explain-code
--- disable-model-invocation: true argument-hint: [file or code] --- # Explain code with visual diagrams and analogies When explaining code, always include: 1. **TL;DR first**: summarize what the code does 2. **Analogy**: compare it to something from everyday life 3. **Walk through the code**: explain step-by-step what happens 4. **Diagram**: use ASCII art appropriate to the code: - Flowchart for control flow / algorithms - Box diagram for data structures / state - Sequence diagram f
development3
misc-configs/claude/skills/04-summarize-unresolved-pr-comments
--- disable-model-invocation: true allowed-tools: Write, Bash(gh:*) --- # Fetch and summarize this PR's UNRESOLVED comments ## Context - OWNER: !`gh repo view --json owner -q .owner.login` - REPO: !`gh repo view --json name -q .name` - PR_NUMBER: !`gh pr view --json number -q .number` ## Your task ### Step 1: Fetch unresolved inline review threads Use this GraphQL query (substitute OWNER, REPO, PR_NUMBER from context above): ```bash gh api graphql -f query=' query($owner: String!, $repo:
tools3
misc-configs/claude/skills/07-guess-whats-next
--- disable-model-invocation: true argument-hint: [hint] allowed-tools: Read --- # Guess What's Next Based on the current conversation, try to predict what the user is about to ask or work on next. ## Hint If $ARGUMENTS is non-empty, treat it as a steering signal: - Bias your ranking and the kinds of guesses you generate toward it (e.g. a hint about "tests" should push test-related predictions higher). - It narrows the area to think about but doesn't override the conversation. - If the hint
tools3
misc-configs/claude/skills/custom-staged-commit-push
--- disable-model-invocation: true context: fork argument-hint: [issue-number] allowed-tools: Bash(git commit:*), Bash(git --no-pager diff:*), Bash(git push:*) model: claude-haiku-4-5 --- # Commit STAGED changes, then push ## Context - Current staged changes only: !`git --no-pager diff --staged` - Issue number argument (empty if none): `$ARGUMENTS` ## Your task Create a commit for the STAGED changes above using `git commit`, then push it with `git push`. REQUIRED: - Subject line: Conven
tools3
misc-configs/claude/skills/custom-staged-commit
--- disable-model-invocation: true context: fork argument-hint: [push] [issue-number] allowed-tools: Bash(git --no-pager diff:*), Bash(git rev-parse:*), Bash(git remote get-url:*), Bash(git commit:*), Bash(git push:*) model: haiku --- # Commit STAGED changes, optionally push ## Context - Current staged changes only: !`git --no-pager diff --staged` - Current branch: !`git rev-parse --abbrev-ref HEAD` - Remote URL: !`git remote get-url origin` - Arguments (issue number and/or `push`, empty if n
tools3
misc-configs/claude/skills/custom-branch-changes-analyze
--- disable-model-invocation: true allowed-tools: Read, Bash(git --no-pager log:*), Bash(git --no-pager diff:*) --- # Get familiar with the current branch's changes ## Context - Commits on this branch: !`git --no-pager log origin/HEAD..HEAD --oneline` - List of changed files: !`git --no-pager diff origin/HEAD...HEAD --stat` - Full diff: !`git --no-pager diff origin/HEAD...HEAD` ## Your task Analyze the changes purely based on the code (do not check the branch name, linked GitHub issues, PR
tools3
misc-configs/claude/skills/custom-staged-summarize
--- disable-model-invocation: true allowed-tools: Read, Bash(git --no-pager diff:*) model: haiku --- # Summarize STAGED changes ## Context - Current staged changes only: !`git --no-pager diff --staged` ## Your task Summarize the changes purely based on the code (do not check the branch name, linked GitHub issues, PR descriptions, or any other contextual clues). REQUIRED: - Prioritize brevity over grammar: Keep messages short, even if grammatically imperfect NEVER: - Run additional Git
tools3
misc-configs/claude/skills/custom-branch-changes-summarize
--- disable-model-invocation: true allowed-tools: Read, Bash(git --no-pager log:*), Bash(git --no-pager diff:*) model: haiku --- # Summarize the current branch's changes ## Context - Commits on this branch: !`git --no-pager log origin/HEAD..HEAD --oneline` - List of changed files: !`git --no-pager diff origin/HEAD...HEAD --stat` - Full diff: !`git --no-pager diff origin/HEAD...HEAD` ## Your task Summarize the changes purely based on the code (do not check the branch name, linked GitHub issu
tools3
misc-configs/claude/skills/custom-branch-changes-analize
--- disable-model-invocation: true allowed-tools: Read, Bash(git --no-pager log:*), Bash(git --no-pager diff:*) --- # Get familiar with the current branch's changes ## Context - Commits on this branch: !`git --no-pager log origin/HEAD..HEAD --oneline` - List of changed files: !`git --no-pager diff origin/HEAD...HEAD --stat` - Full diff: !`git --no-pager diff origin/HEAD...HEAD` ## Your task Analyze the changes purely based on the code (do not check the branch name, linked GitHub issues, PR
tools3
misc-configs/claude/skills/custom-guess-whats-next
--- disable-model-invocation: true argument-hint: [hint] allowed-tools: Read --- # Guess What's Next Based on the current conversation, try to predict what the user is about to ask or work on next. ## Hint If $ARGUMENTS is non-empty, treat it as a steering signal: - Bias your ranking and the kinds of guesses you generate toward it (e.g. a hint about "tests" should push test-related predictions higher). - It narrows the area to think about but doesn't override the conversation. - If the hint
tools3
misc-configs/claude/skills/custom-reminder
--- disable-model-invocation: true --- # Reminder before continuing ## Your task REMEMBER: - Run ALL Git commands from the current working directory. NEVER `cd` into other directories to run Git. Git automatically finds the repo root. Confirm you've understood the above before continuing.
data-ai3
misc-configs/claude/skills/custom-staged-commit-dont-push
--- disable-model-invocation: true context: fork argument-hint: [issue-number] allowed-tools: Bash(git commit:*), Bash(git --no-pager diff:*) model: claude-haiku-4-5 --- # Commit STAGED changes, don't push ## Context - Current staged changes only: !`git --no-pager diff --staged` - Issue number argument (empty if none): `$ARGUMENTS` ## Your task Create a commit for the STAGED changes above using `git commit`. REQUIRED: - Subject line: Conventional commits format, e.g. `type(scope): descr
tools3
misc-configs/claude/skills/custom-unresolved-pr-comments-summarize
--- disable-model-invocation: true allowed-tools: Write, Bash(gh:*) --- # Fetch and summarize this PR's UNRESOLVED comments ## Context - OWNER: !`gh repo view --json owner -q .owner.login` - REPO: !`gh repo view --json name -q .name` - PR_NUMBER: !`gh pr view --json number -q .number` ## Your task ### Step 1: Fetch unresolved inline review threads Use this GraphQL query (substitute OWNER, REPO, PR_NUMBER from context above): ```bash gh api graphql -f query=' query($owner: String!, $repo:
tools3
misc-configs/claude/skills/custom-staged-create-branch
--- disable-model-invocation: true context: fork allowed-tools: Bash(git checkout:*), Bash(git --no-pager diff:*) model: haiku --- # New branch for STAGED changes ## Context - Current Git diff (staged changes only): !`git --no-pager diff --staged` ## Your task Based on the above STAGED changes, create a new branch with a descriptive name. ALWAYS: - Prioritize brevity over grammar: Keep the branch name short, even if grammatically imperfect - Name the branch `<type>/<short-kebab-descript
tools3
misc-configs/claude/skills/custom-explain-code
--- disable-model-invocation: true argument-hint: [file or code] allowed-tools: Read --- # Explain code with visual diagrams and analogies When explaining code, always include: 1. **TL;DR first**: summarize what the code does 2. **Analogy**: compare it to something from everyday life 3. **Walk through the code**: explain step-by-step what happens 4. **Diagram**: use ASCII art appropriate to the code: - Flowchart for control flow / algorithms - Box diagram for data structures / state
tools3