External/SuperClaude
1
0
Fork 0
mirror of https://github.com/SuperClaude-Org/SuperClaude_Framework.git synced 2025-12-29 16:16:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

🔧 Fix command syntax inconsistencies and improve documentation clarity

Browse Source 
## Command Syntax Standardization
- Fix lowercase "superclaude" → "SuperClaude" in installation.md
- Distinguish between terminal commands (SuperClaude install) and Claude Code commands (/sc:*)
- Add clear command context headers to all major documentation files

## Documentation Improvements
- Add command reference tables to key guides
- Create visual distinction markers (🖥️ Terminal vs 💬 Claude Code)
- Update verification sections with proper command separation
- Fix content duplications in Developer-Guide and Getting-Started files

## Cross-Reference Updates
- Standardize all documentation links to use Docs/ prefix structure
- Replace invalid email addresses with anton.knoery@gmail.com
- Remove non-existent team references from security documentation

## Files Enhanced
- Getting-Started: installation.md, quick-start.md with command clarity
- User-Guide: commands.md with comprehensive command context
- Reference: troubleshooting.md, common-issues.md with mixed command support
- Root files: README.md, CONTRIBUTING.md, SECURITY.md link updates

This resolves command confusion between installation (terminal) and development (/sc:) commands.

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
NomenAK
2025-08-18 12:45:06 +02:00
parent d2f4ef43e4
commit 1eab5e3bc4
20 changed files with 286 additions and 101 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
Docs/Developer-Guide/contributing-code.md
View File

@@ -597,18 +597,11 @@ Brief description of changes and motivation
- **Performance**: No significant performance degradation
**Addressing Feedback:**
```bash
# 1. Make requested changes
# 2. Commit with clear messages
git add .
git commit -m "address review: improve error handling in component loader"
# 3. Push updates
git push origin feature/your-feature-name
# 4. Respond to review comments
# 5. Request re-review when ready
```
1. Make requested changes to your code
2. Commit with clear messages describing the fixes
3. Push updates to your feature branch
4. Respond to review comments explaining your changes
5. Request re-review when ready
## 📋 Comprehensive Contributor Onboarding Checklist