Expand toolkit to 135 agents, 120 plugins, 796 total files
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
This commit is contained in:
6
plugins/commit-commands/.claude-plugin/plugin.json
Normal file
6
plugins/commit-commands/.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,6 @@
|
||||
{
|
||||
"name": "commit-commands",
|
||||
"version": "1.0.0",
|
||||
"description": "Advanced commit workflows with smart staging and push automation",
|
||||
"commands": ["commands/commit-push.md", "commands/amend.md"]
|
||||
}
|
||||
28
plugins/commit-commands/commands/amend.md
Normal file
28
plugins/commit-commands/commands/amend.md
Normal file
@@ -0,0 +1,28 @@
|
||||
Amend the most recent commit with additional changes or an updated message.
|
||||
|
||||
## Steps
|
||||
|
||||
|
||||
1. Verify the last commit has not been pushed to remote:
|
||||
2. If there are additional file changes to include:
|
||||
3. Decide whether to update the commit message:
|
||||
4. Verify the amended commit looks correct:
|
||||
5. If the original commit was already pushed:
|
||||
|
||||
## Format
|
||||
|
||||
|
||||
```
|
||||
Amended Commit: <hash>
|
||||
Message: <commit message>
|
||||
Files Changed: <list>
|
||||
Force Push Required: <yes|no>
|
||||
```
|
||||
|
||||
|
||||
## Rules
|
||||
|
||||
- Never amend a commit that has been pushed without explicit user approval.
|
||||
- Always verify no unintended changes are included in the amendment.
|
||||
- Preserve the original commit type (feat, fix, etc.) unless instructed otherwise.
|
||||
|
||||
30
plugins/commit-commands/commands/commit-push.md
Normal file
30
plugins/commit-commands/commands/commit-push.md
Normal file
@@ -0,0 +1,30 @@
|
||||
Stage, commit, and push changes with an auto-generated conventional commit message.
|
||||
|
||||
## Steps
|
||||
|
||||
|
||||
1. Run `git status` to see all modified, staged, and untracked files.
|
||||
2. Run `git diff` to review all changes (staged and unstaged).
|
||||
3. Analyze the changes to determine the commit type:
|
||||
4. Generate a conventional commit message:
|
||||
5. Stage the appropriate files (avoid staging secrets or build artifacts).
|
||||
6. Create the commit with the generated message.
|
||||
7. Push to the remote branch with `git push origin HEAD`.
|
||||
|
||||
## Format
|
||||
|
||||
|
||||
```
|
||||
type(scope): description
|
||||
|
||||
Why: <explanation of motivation>
|
||||
Refs: #<issue number> (if applicable)
|
||||
```
|
||||
|
||||
|
||||
## Rules
|
||||
|
||||
- Never commit .env files, credentials, or API keys.
|
||||
- Commit message subject must be under 72 characters.
|
||||
- Use present tense in commit messages ("add feature" not "added feature").
|
||||
|
||||
Reference in New Issue
Block a user