namnam-skills 1.0.0 → 1.0.1

package/src/templates/platforms/AGENTS.md

@@ -285,6 +285,53 @@ When using Cursor, Windsurf, Cline, or other agents:
 - Reference previous work
 - Store important context
 
+### @conversation System
+
+The project supports cross-conversation context via the `@conversation` feature.
+
+#### Recognizing References
+When users include `@conversation:<id>` in their messages:
+```
+Pattern: @conversation[:\s]+([a-zA-Z0-9_-]+)
+Examples:
+  - @conversation:abc123
+  - @conversation abc123
+  - Based on @conversation:auth01, implement...
+```
+
+#### Loading Context
+Load referenced conversation context:
+```bash
+# Get formatted context
+namnam conv context <id>
+
+# Or read directly from
+.claude/conversations/<full-id>/context.md
+```
+
+#### Using Context
+When conversation context is loaded:
+1. Treat it as authoritative prior decisions
+2. Build upon the context, don't contradict it
+3. Reference specific points when relevant
+4. Ask for clarification if context seems outdated
+
+#### Saving Conversations
+When a session contains important decisions, suggest saving:
+```bash
+namnam conv save -t "Title" -s "Brief summary"
+```
+
+#### Storage Location
+```
+.claude/conversations/
+├── index.json           # Conversation index
+└── conv_xxx_yyy/        # Individual conversation
+    ├── meta.json        # Metadata
+    ├── context.md       # Loadable context
+    └── full.md          # Full log (optional)
+```
+
 ---
 
 ## Error Handling

package/src/templates/core/code-review.md

@@ -1,70 +0,0 @@
-# /code-review - Multi-Aspect Code Review
-
-> Comprehensive code review using parallel expert agents
-
-## Usage
-
-```
-/code-review
-/code-review src/auth
-/code-review --focus security
-```
-
-## Instructions
-
-When the user invokes `/code-review`:
-
-### Step 1: Identify Target
-
-If no path provided, review recent changes:
-```bash
-git diff --name-only HEAD~1
-```
-
-### Step 2: Spawn Review Agents
-
-Run these in parallel:
-
-| Agent | Focus |
-|-------|-------|
-| Architecture Reviewer | Design patterns, coupling |
-| Code Quality Reviewer | Readability, duplication |
-| Security Reviewer | Vulnerabilities, OWASP |
-| Performance Reviewer | Bottlenecks, optimization |
-| Testing Reviewer | Coverage, quality |
-| Documentation Reviewer | Comments, API docs |
-
-### Step 3: Aggregate Results
-
-```markdown
-## Code Review Report
-
-### Summary
-- **Files reviewed**: 12
-- **Issues found**: 8
-- **Severity**: 2 Critical, 3 High, 3 Medium
-
-### Critical Issues 🔴
-| File:Line | Issue | Recommendation |
-|-----------|-------|----------------|
-| auth.ts:42 | SQL injection risk | Use parameterized query |
-
-### High Priority 🟡
-| File:Line | Issue | Recommendation |
-|-----------|-------|----------------|
-| utils.ts:15 | No input validation | Add validation |
-
-### Medium Priority 🟢
-| File:Line | Issue | Recommendation |
-|-----------|-------|----------------|
-| form.tsx:88 | Missing error handling | Add try-catch |
-
-### Strengths ✨
-- Good separation of concerns
-- Consistent naming conventions
-
-### Recommendations
-1. Address critical security issues immediately
-2. Add input validation to all user inputs
-3. Increase test coverage to 80%
-```

package/src/templates/core/git-commit.md

@@ -1,57 +0,0 @@
-# /git:commit - Smart Git Commit
-
-> Create intelligent git commits with conventional commit format
-
-## Usage
-
-```
-/git:commit
-/git:commit fix login validation
-```
-
-## Instructions
-
-When the user invokes `/git:commit`:
-
-1. **Check git status**:
-   ```bash
-   git status --porcelain
-   git diff --staged --stat
-   ```
-
-2. **If no staged changes**:
-   - Show modified/untracked files
-   - Ask what to stage
-
-3. **Analyze changes**:
-   - Parse diff to understand changes
-   - Identify commit type: feat, fix, refactor, docs, test, chore
-
-4. **Generate commit message**:
-   - Follow conventional commits: `<type>(<scope>): <subject>`
-   - Keep subject under 50 chars
-   - Add body for complex changes
-
-5. **Execute**:
-   ```bash
-   git commit -m "$(cat <<'EOF'
-   <type>(<scope>): <subject>
-
-   <body>
-
-   Co-Authored-By: Claude <noreply@anthropic.com>
-   EOF
-   )"
-   ```
-
-## Commit Types
-
-| Type | When to use |
-|------|-------------|
-| `feat` | New feature |
-| `fix` | Bug fix |
-| `docs` | Documentation |
-| `style` | Formatting |
-| `refactor` | Code restructure |
-| `test` | Tests |
-| `chore` | Maintenance |

package/src/templates/core/git-push.md

@@ -1,53 +0,0 @@
-# /git:push - Safe Git Push
-
-> Push commits to remote with safety checks
-
-## Usage
-
-```
-/git:push
-/git:push origin main
-```
-
-## Instructions
-
-When the user invokes `/git:push`:
-
-1. **Pre-push checks**:
-   ```bash
-   git status
-   git log origin/HEAD..HEAD --oneline
-   ```
-
-2. **Safety validations**:
-   - Check if branch is protected
-   - Warn if pushing to main/master
-   - Check for uncommitted changes
-
-3. **Execute push**:
-   ```bash
-   git push -u origin <branch>
-   ```
-
-4. **Post-push summary**:
-   ```markdown
-   ## Push Complete
-
-   **Branch**: feature/auth → origin/feature/auth
-   **Commits pushed**: 3
-
-   ### Commits
-   - abc123 feat(auth): add login
-   - def456 fix(auth): validate email
-   - ghi789 test(auth): add tests
-
-   ### Next Steps
-   - Create PR: `gh pr create`
-   - Or use `/commit-push-pr` for full workflow
-   ```
-
-## Safety
-
-- Never force push without explicit request
-- Warn before pushing to protected branches
-- Show what will be pushed before confirming

package/src/templates/core/git-status.md

@@ -1,48 +0,0 @@
-# /git:status - Enhanced Git Status
-
-> Intelligent git status with insights
-
-## Usage
-
-```
-/git:status
-```
-
-## Instructions
-
-When the user invokes `/git:status`:
-
-1. **Get status**:
-   ```bash
-   git status
-   git diff --stat
-   ```
-
-2. **Analyze and present**:
-   ```markdown
-   ## Git Status
-
-   ### Branch
-   **Current**: feature/auth
-   **Tracking**: origin/feature/auth (2 ahead, 1 behind)
-
-   ### Changes
-
-   #### Staged (ready to commit)
-   - ✅ src/auth/login.ts (+42, -15)
-   - ✅ src/utils/validate.ts (+10, -2)
-
-   #### Modified (not staged)
-   - 📝 src/components/Form.tsx
-   - 📝 src/hooks/useAuth.ts
-
-   #### Untracked
-   - ❓ src/new-file.ts
-   - ❓ tests/auth.test.ts
-
-   ### Suggestions
-   - Run `git add .` to stage all changes
-   - Run `/git:commit` to commit staged changes
-   ```
-
-3. **Provide actionable insights**

package/src/templates/core/validate-and-fix.md

@@ -1,69 +0,0 @@
-# /validate-and-fix - Quality Checks & Auto-Fix
-
-> Run quality checks and automatically fix issues
-
-## Usage
-
-```
-/validate-and-fix
-/validate-and-fix --lint
-/validate-and-fix --types
-/validate-and-fix --all
-```
-
-## Instructions
-
-When the user invokes `/validate-and-fix`:
-
-### Step 1: Detect Project Type
-
-```bash
-ls package.json tsconfig.json .eslintrc* .prettierrc*
-```
-
-### Step 2: Run Checks in Parallel
-
-| Check | Command | Auto-fix |
-|-------|---------|----------|
-| Lint | `npm run lint` | `npm run lint -- --fix` |
-| Types | `npx tsc --noEmit` | Manual fixes |
-| Format | `npx prettier --check .` | `npx prettier --write .` |
-| Tests | `npm test` | Manual fixes |
-
-### Step 3: Auto-Fix What's Possible
-
-```bash
-# Fix linting
-npm run lint -- --fix
-
-# Fix formatting
-npx prettier --write .
-```
-
-### Step 4: Report Results
-
-```markdown
-## Validation Results
-
-### ✅ Passed
-- Formatting (auto-fixed 5 files)
-- Linting (auto-fixed 3 issues)
-
-### ❌ Needs Manual Fix
-| Type | File:Line | Issue |
-|------|-----------|-------|
-| TypeScript | api.ts:42 | Type 'string' not assignable |
-| Test | auth.test.ts:15 | Expected true, got false |
-
-### Summary
-- **Auto-fixed**: 8 issues
-- **Manual fixes needed**: 2 issues
-
-### Next Steps
-1. Fix TypeScript error in api.ts:42
-2. Update failing test in auth.test.ts:15
-```
-
-### Step 5: Re-validate
-
-Run checks again to confirm all issues resolved.