Compare commits

...

2 Commits

Author SHA1 Message Date
rootiest 9f524694cb Merge pull request 'feat(functions): add claude-docs and claude-pr helper functions' (#10) from feat/claude-helper-functions into main
Reviewed-on: #10
2026-05-08 17:39:40 +00:00
rootiest 37f35ce0a0 feat(functions): add claude-docs and claude-pr helper functions
Add two Claude Code helper functions to streamline common dev workflows:
- `claude-docs`: triggers Claude to sync README.md with recent session changes
- `claude-pr`: triggers Claude to create a branch, commit, push, and open a PR

Also add `.claude` to .gitignore and document both functions in README.md.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-08 13:37:41 -04:00
4 changed files with 9 additions and 0 deletions
+1
View File
@@ -35,3 +35,4 @@ OLD/
# Auto-managed by fish; contains machine-local state and universal vars
fish_variables
.claude
+2
View File
@@ -299,6 +299,8 @@ rm -f file.txt # Falls through to standard rm -f
| `gemini-resume` | Resume Gemini CLI session from `.gemini_session` in CWD |
| `code-resume` | Smart resume — tries Claude then Gemini, falls back to picker |
| `superpowers [on\|off]` | Enable/disable the Superpowers extension for Claude and Gemini |
| `claude-docs` | Ask Claude to sync `README.md` with recent session changes |
| `claude-pr` | Create a branch, commit, push, and open a PR via Claude |
### Fetch & Info
+3
View File
@@ -0,0 +1,3 @@
function claude-docs --description 'Claude-code: Sync README with recent changes'
claude "Analyze the recent changes and update the README.md to ensure all features, setup instructions, and examples are 100% accurate. Prune any obsolete information."
end
+3
View File
@@ -0,0 +1,3 @@
function claude-pr --description 'Claude-code: New branch, commit, push, and PR'
claude "Act as a senior engineer. Execute this sequence: 1. Create a new git branch (kebab-case). 2. Stage changes and write a Conventional Commit message. 3. Self-verify the changes by running relevant build/test commands or linting. 4. Push to remote. 5. Create a PR to 'main' including a summary of changes and a 'Manual Verification' section containing a Markdown checklist (- [ ]) of specific, bite-sized steps required to manually verify the functionality."
end