You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: improve CLI best practices organization in workflow rules (#3)
- Organize | cat requirements into clear categories
- Add comprehensive coverage for GitHub CLI commands
- Improve readability and maintainability of the rules
- Add more specific examples for different command types
Copy file name to clipboardExpand all lines: .cursor/rules/workflow.mdc
+8-9Lines changed: 8 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -119,12 +119,11 @@ When you request to "initialize git repo", I will perform the following steps:
119
119
### CLI Best Practices
120
120
- **Always use SSH format for git remotes** (`git@github.com:user/repo.git`) rather than HTTPS format to leverage SSH key authentication instead of token-based authentication
121
121
- **CRITICAL: Always append `| cat` to commands that use pagers** to prevent interactive paging that requires manual exit with `:q`. This is MANDATORY for:
- **GitHub CLI API commands**: `gh api | cat` (when expecting large responses or to prevent potential paging)
127
+
- **Man pages**: `man git | cat`, `man gh | cat`
128
+
- **Any command that might output more than a screen's worth of content**
129
+
- **Rule Exception**: Only omit `| cat` when you specifically need interactive features (like `git add -p` for patch mode) or when using action commands that don't display large amounts of output (like `gh pr create`, `gh issue create`, `gh repo create`)
0 commit comments