Skip to content

Commit adc20d2

Browse files
jdiegosierrajdiegosierra
authored
Merge branch 'main' into example/test-contributor-report-action
2 parents 8abc90d + e92e3ab commit adc20d2

50 files changed

Lines changed: 35813 additions & 5417 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.agents/skills/find-skills/SKILL.md‎

Lines changed: 137 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,137 @@
1+
---
2+
name: find-skills
3+
description:
4+
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is
5+
there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is
6+
looking for functionality that might exist as an installable skill.
7+
---
8+
9+
# Find Skills
10+
11+
This skill helps you discover and install skills from the open agent skills ecosystem.
12+
13+
## When to Use This Skill
14+
15+
Use this skill when the user:
16+
17+
- Asks "how do I do X" where X might be a common task with an existing skill
18+
- Says "find a skill for X" or "is there a skill for X"
19+
- Asks "can you do X" where X is a specialized capability
20+
- Expresses interest in extending agent capabilities
21+
- Wants to search for tools, templates, or workflows
22+
- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
23+
24+
## What is the Skills CLI?
25+
26+
The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages
27+
that extend agent capabilities with specialized knowledge, workflows, and tools.
28+
29+
**Key commands:**
30+
31+
- `npx skills find [query]` - Search for skills interactively or by keyword
32+
- `npx skills add <package>` - Install a skill from GitHub or other sources
33+
- `npx skills check` - Check for skill updates
34+
- `npx skills update` - Update all installed skills
35+
36+
**Browse skills at:** https://skills.sh/
37+
38+
## How to Help Users Find Skills
39+
40+
### Step 1: Understand What They Need
41+
42+
When a user asks for help with something, identify:
43+
44+
1. The domain (e.g., React, testing, design, deployment)
45+
2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
46+
3. Whether this is a common enough task that a skill likely exists
47+
48+
### Step 2: Search for Skills
49+
50+
Run the find command with a relevant query:
51+
52+
```bash
53+
npx skills find [query]
54+
```
55+
56+
For example:
57+
58+
- User asks "how do I make my React app faster?" → `npx skills find react performance`
59+
- User asks "can you help me with PR reviews?" → `npx skills find pr review`
60+
- User asks "I need to create a changelog" → `npx skills find changelog`
61+
62+
The command will return results like:
63+
64+
```
65+
Install with npx skills add <owner/repo@skill>
66+
67+
vercel-labs/agent-skills@vercel-react-best-practices
68+
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
69+
```
70+
71+
### Step 3: Present Options to the User
72+
73+
When you find relevant skills, present them to the user with:
74+
75+
1. The skill name and what it does
76+
2. The install command they can run
77+
3. A link to learn more at skills.sh
78+
79+
Example response:
80+
81+
```
82+
I found a skill that might help! The "vercel-react-best-practices" skill provides
83+
React and Next.js performance optimization guidelines from Vercel Engineering.
84+
85+
To install it:
86+
npx skills add vercel-labs/agent-skills@vercel-react-best-practices
87+
88+
Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
89+
```
90+
91+
### Step 4: Offer to Install
92+
93+
If the user wants to proceed, you can install the skill for them:
94+
95+
```bash
96+
npx skills add <owner/repo@skill> -g -y
97+
```
98+
99+
The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
100+
101+
## Common Skill Categories
102+
103+
When searching, consider these common categories:
104+
105+
| Category | Example Queries |
106+
| --------------- | ---------------------------------------- |
107+
| Web Development | react, nextjs, typescript, css, tailwind |
108+
| Testing | testing, jest, playwright, e2e |
109+
| DevOps | deploy, docker, kubernetes, ci-cd |
110+
| Documentation | docs, readme, changelog, api-docs |
111+
| Code Quality | review, lint, refactor, best-practices |
112+
| Design | ui, ux, design-system, accessibility |
113+
| Productivity | workflow, automation, git |
114+
115+
## Tips for Effective Searches
116+
117+
1. **Use specific keywords**: "react testing" is better than just "testing"
118+
2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
119+
3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
120+
121+
## When No Skills Are Found
122+
123+
If no relevant skills exist:
124+
125+
1. Acknowledge that no existing skill was found
126+
2. Offer to help with the task directly using your general capabilities
127+
3. Suggest the user could create their own skill with `npx skills init`
128+
129+
Example:
130+
131+
```
132+
I searched for skills related to "xyz" but didn't find any matches.
133+
I can still help you with this task directly! Would you like me to proceed?
134+
135+
If this is something you do often, you could create your own skill:
136+
npx skills init my-xyz-skill
137+
```

‎.agents/skills/git-commit/SKILL.md‎

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
---
2+
name: git-commit
3+
description:
4+
'Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when
5+
user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope
6+
from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional
7+
type/scope/description overrides, (4) Intelligent file staging for logical grouping'
8+
license: MIT
9+
allowed-tools: Bash
10+
---
11+
12+
# Git Commit with Conventional Commits
13+
14+
## Overview
15+
16+
Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to
17+
determine appropriate type, scope, and message.
18+
19+
## Conventional Commit Format
20+
21+
```
22+
<type>[optional scope]: <description>
23+
24+
[optional body]
25+
26+
[optional footer(s)]
27+
```
28+
29+
## Commit Types
30+
31+
| Type | Purpose |
32+
| ---------- | ------------------------------ |
33+
| `feat` | New feature |
34+
| `fix` | Bug fix |
35+
| `docs` | Documentation only |
36+
| `style` | Formatting/style (no logic) |
37+
| `refactor` | Code refactor (no feature/fix) |
38+
| `perf` | Performance improvement |
39+
| `test` | Add/update tests |
40+
| `build` | Build system/dependencies |
41+
| `ci` | CI/config changes |
42+
| `chore` | Maintenance/misc |
43+
| `revert` | Revert commit |
44+
45+
## Breaking Changes
46+
47+
```
48+
# Exclamation mark after type/scope
49+
feat!: remove deprecated endpoint
50+
51+
# BREAKING CHANGE footer
52+
feat: allow config to extend other configs
53+
54+
BREAKING CHANGE: `extends` key behavior changed
55+
```
56+
57+
## Workflow
58+
59+
### 1. Analyze Diff
60+
61+
```bash
62+
# If files are staged, use staged diff
63+
git diff --staged
64+
65+
# If nothing staged, use working tree diff
66+
git diff
67+
68+
# Also check status
69+
git status --porcelain
70+
```
71+
72+
### 2. Stage Files (if needed)
73+
74+
If nothing is staged or you want to group changes differently:
75+
76+
```bash
77+
# Stage specific files
78+
git add path/to/file1 path/to/file2
79+
80+
# Stage by pattern
81+
git add *.test.*
82+
git add src/components/*
83+
84+
# Interactive staging
85+
git add -p
86+
```
87+
88+
**Never commit secrets** (.env, credentials.json, private keys).
89+
90+
### 3. Generate Commit Message
91+
92+
Analyze the diff to determine:
93+
94+
- **Type**: What kind of change is this?
95+
- **Scope**: What area/module is affected?
96+
- **Description**: One-line summary of what changed (present tense, imperative mood, <72 chars)
97+
98+
### 4. Execute Commit
99+
100+
```bash
101+
# Single line
102+
git commit -m "<type>[scope]: <description>"
103+
104+
# Multi-line with body/footer
105+
git commit -m "$(cat <<'EOF'
106+
<type>[scope]: <description>
107+
108+
<optional body>
109+
110+
<optional footer>
111+
EOF
112+
)"
113+
```
114+
115+
## Best Practices
116+
117+
- One logical change per commit
118+
- Present tense: "add" not "added"
119+
- Imperative mood: "fix bug" not "fixes bug"
120+
- Reference issues: `Closes #123`, `Refs #456`
121+
- Keep description under 72 characters
122+
123+
## Git Safety Protocol
124+
125+
- NEVER update git config
126+
- NEVER run destructive commands (--force, hard reset) without explicit request
127+
- NEVER skip hooks (--no-verify) unless user asks
128+
- NEVER force push to main/master
129+
- If commit fails due to hooks, fix and create NEW commit (don't amend)

0 commit comments

Comments
 (0)