@sk8metal/michi-cli 0.11.0 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. package/README.md +3 -10
  2. package/dist/scripts/constants/environments.d.ts +1 -1
  3. package/dist/scripts/constants/environments.d.ts.map +1 -1
  4. package/dist/scripts/constants/environments.js +0 -20
  5. package/dist/scripts/constants/environments.js.map +1 -1
  6. package/dist/scripts/utils/template-finder.d.ts +2 -2
  7. package/dist/scripts/utils/template-finder.d.ts.map +1 -1
  8. package/dist/scripts/utils/template-finder.js +3 -8
  9. package/dist/scripts/utils/template-finder.js.map +1 -1
  10. package/dist/src/cli.d.ts.map +1 -1
  11. package/dist/src/cli.js +0 -8
  12. package/dist/src/cli.js.map +1 -1
  13. package/dist/src/commands/init.d.ts +0 -4
  14. package/dist/src/commands/init.d.ts.map +1 -1
  15. package/dist/src/commands/init.js +6 -30
  16. package/dist/src/commands/init.js.map +1 -1
  17. package/dist/src/commands/setup-existing.d.ts +2 -6
  18. package/dist/src/commands/setup-existing.d.ts.map +1 -1
  19. package/dist/src/commands/setup-existing.js +8 -142
  20. package/dist/src/commands/setup-existing.js.map +1 -1
  21. package/docs/getting-started/configuration.md +0 -29
  22. package/docs/getting-started/quick-start.md +2 -2
  23. package/docs/guides/workflow.md +1 -1
  24. package/docs/reference/cli.md +0 -4
  25. package/docs/troubleshooting.md +0 -45
  26. package/package.json +1 -3
  27. package/scripts/__tests__/create-project.test.ts +12 -12
  28. package/scripts/__tests__/setup-existing-project.test.ts +22 -22
  29. package/scripts/constants/__tests__/environments.test.ts +7 -50
  30. package/scripts/constants/environments.ts +1 -27
  31. package/scripts/template/__tests__/renderer.test.ts +21 -21
  32. package/scripts/utils/template-finder.ts +5 -11
  33. package/docs/guides/ai-tools.md +0 -311
  34. package/templates/cline/rules/atlassian-integration.md +0 -36
  35. package/templates/cline/rules/michi-core.md +0 -56
  36. package/templates/codex/AGENTS.override.md +0 -277
  37. package/templates/codex/prompts/confluence-sync.md +0 -177
  38. package/templates/codex/rules/README.md +0 -210
  39. package/templates/cursor/commands/kiro/kiro-spec-impl.md +0 -244
  40. package/templates/cursor/commands/kiro/kiro-spec-tasks.md +0 -354
  41. package/templates/cursor/commands/michi/confluence-sync.md +0 -76
  42. package/templates/cursor/commands/michi/project-switch.md +0 -69
  43. package/templates/cursor/commands/michi/spec-tasks.md +0 -117
  44. package/templates/cursor/rules/atlassian-mcp.mdc +0 -188
  45. package/templates/cursor/rules/github-ssot.mdc +0 -151
  46. package/templates/cursor/rules/multi-project.mdc +0 -81
  47. package/templates/gemini/commands/README.md +0 -41
  48. package/templates/gemini/rules/GEMINI.md +0 -80
package/templates/gemini/rules/GEMINI.md DELETED
@@ -1,80 +0,0 @@
1
- # Michi Core Principles for Gemini CLI
2
-
3
- ## Development Guidelines
4
- {{DEV_GUIDELINES}}
5
-
6
- ## Language
7
- All generated documents should be in: **{{LANG_CODE}}**
8
-
9
- Reference the language field in {{KIRO_DIR}}/project.json.
10
-
11
- ## Single Source of Truth (SSoT)
12
-
13
- ### GitHub as SSoT
14
- - **All specifications are managed in GitHub** ({{KIRO_DIR}}/specs/)
15
- - Confluence is **reference and approval only** (editing is GitHub only)
16
- - Avoid duplicate management
17
-
18
- ### Data Flow
19
- ```
20
- GitHub ({{KIRO_DIR}}/specs/) ← Source of truth (editable)
21
- ↓ sync
22
- Confluence ← Display and approval (read-only)
23
- ```
24
-
25
- ## Multi-Project Management
26
-
27
- ### Project Identification
28
- - All operations reference {{KIRO_DIR}}/project.json
29
- - Dynamically use project ID, JIRA key, Confluence labels
30
- - Project ID: {{PROJECT_ID}}
31
-
32
- ### Naming Conventions
33
-
34
- #### Confluence Pages
35
- - Format: `[{projectName}] {document_type}`
36
- - Example: `[{{PROJECT_ID}}] Requirements`
37
-
38
- #### JIRA Epic/Story
39
- - Format: `[{JIRA_KEY}] {title}`
40
- - Use project metadata from {{KIRO_DIR}}/project.json
41
-
42
- ## Project Structure
43
-
44
- - Project metadata: {{KIRO_DIR}}/project.json
45
- - Specifications: {{KIRO_DIR}}/specs/
46
- - Templates: {{KIRO_DIR}}/settings/templates/
47
- - Steering: {{KIRO_DIR}}/steering/
48
-
49
- ## Workflow Integration
50
-
51
- ### Spec Generation
52
- Use Gemini CLI to generate specifications in {{KIRO_DIR}}/specs/
53
-
54
- ### Git Integration
55
- ```bash
56
- # After spec generation
57
- git add {{KIRO_DIR}}/specs/
58
- git commit -m "docs: Add <feature> specification"
59
- git push
60
- ```
61
-
62
- ### Confluence Sync
63
- Sync GitHub specs to Confluence using Michi commands:
64
- ```bash
65
- # Example: Sync requirements
66
- npm run confluence:sync
67
- ```
68
-
69
- ## Best Practices
70
-
71
- 1. **Always reference project.json** for project-specific metadata
72
- 2. **Use SSoT principle** - Edit in GitHub, reference in Confluence
73
- 3. **Follow naming conventions** for consistency
74
- 4. **Generate specs incrementally** - Requirements → Design → Tasks
75
- 5. **Commit frequently** to GitHub
76
-
77
- ## Additional Context
78
-
79
- For Atlassian integration rules and multi-project management details,
80
- see extensions in {{KIRO_DIR}}/.gemini/extensions/