feat: add Learning Paths, examples, and project governance files
### New Content - Learning Paths section in README (Junior/Senior/Power User/PM tracks) - examples/ folder with 18 ready-to-use templates: - 4 agents (code-reviewer, test-writer, security-auditor, refactoring) - 2 skills (TDD workflow, security checklist) - 3 commands (commit, review-pr, generate-tests) - 4 hooks (bash + PowerShell for security, formatting) - 3 config templates (settings, MCP, gitignore) - 2 memory templates (project + personal CLAUDE.md) ### Governance - CHANGELOG.md: Version history (1.0.0 → 1.1.0 → Unreleased) - CONTRIBUTING.md: Contribution guidelines for community ### Documentation - llms.txt: Updated structure with new files/folders This update makes the guide more actionable with concrete templates and provides clear learning paths for different skill levels. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
a4eed95f47
commit
b2acc9b115
24 changed files with 1744 additions and 4 deletions
68
examples/commands/commit.md
Normal file
68
examples/commands/commit.md
Normal file
|
|
@ -0,0 +1,68 @@
|
|||
# Conventional Commit
|
||||
|
||||
Generate a conventional commit message for staged changes.
|
||||
|
||||
## Instructions
|
||||
|
||||
1. Run `git diff --cached` to see staged changes
|
||||
2. Analyze the nature of changes
|
||||
3. Generate a commit message following the format below
|
||||
|
||||
## Commit Format
|
||||
|
||||
```
|
||||
<type>(<scope>): <subject>
|
||||
|
||||
[optional body]
|
||||
|
||||
[optional footer]
|
||||
```
|
||||
|
||||
### Types
|
||||
- `feat`: New feature
|
||||
- `fix`: Bug fix
|
||||
- `docs`: Documentation only
|
||||
- `style`: Formatting, missing semicolons, etc.
|
||||
- `refactor`: Code change that neither fixes nor adds feature
|
||||
- `perf`: Performance improvement
|
||||
- `test`: Adding missing tests
|
||||
- `chore`: Maintenance tasks
|
||||
|
||||
### Rules
|
||||
- Subject: imperative mood, no period, max 50 chars
|
||||
- Body: explain WHAT and WHY, not HOW
|
||||
- Footer: breaking changes, issue references
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
feat(auth): add password reset functionality
|
||||
|
||||
Implement password reset flow with email verification.
|
||||
Users can now request a reset link and set new password.
|
||||
|
||||
Closes #123
|
||||
```
|
||||
|
||||
```
|
||||
fix(api): prevent race condition in order processing
|
||||
|
||||
Add mutex lock to ensure orders are processed sequentially.
|
||||
This fixes duplicate charge issues reported by users.
|
||||
|
||||
Fixes #456
|
||||
```
|
||||
|
||||
```
|
||||
refactor(cart): extract pricing logic to separate module
|
||||
|
||||
No functional changes. Improves testability and
|
||||
separates concerns for future discount feature.
|
||||
```
|
||||
|
||||
## Execution
|
||||
|
||||
After analyzing staged changes, suggest a commit message.
|
||||
Ask for confirmation before executing `git commit -m "..."`.
|
||||
|
||||
$ARGUMENTS
|
||||
Loading…
Add table
Add a link
Reference in a new issue