rootiest
859f14a6e9
Audits every function's interaction with the C1-shadowed commands (uses-shadow/bypasses-shadow) and general hazards (destructive, network, blocking-prompt) per the CLASSIFICATION schema. Delegated the initial mechanical sweep to agy, then reviewed every file by hand: fixed a systemic double-blank-comment-line formatting bug from the delegate pass, and corrected several judgment errors found on review -- three false blocking-prompt tags where a fish 'read' was consuming piped input rather than waiting on a terminal (open-url.fish, sbver.fish, play-media.fish, now untagged entirely), a blocking-prompt tag on mkrep.fish despite its documented --yes escape hatch, an untagged read in jobrunner.fish's own baseless blocking-prompt claim (removed, along with a destructive tag on cleanup of its own mktemp output -- the schema explicitly excludes that), the same own-output-cleanup false positive on _zellij_dump_log.fish's destructive tag, an interactive fzf-gated confirmation on logs.fish and replay.fish's piped read misread the same way as the first three, and a uses-shadow(mkdir) on mkcd.fish that actually belongs to the _fish_mkdir_p helper it delegates to, not to mkcd itself.
28 lines
1.1 KiB
Fish
28 lines
1.1 KiB
Fish
# Copyright (C) 2026 Rootiest
|
|
# SPDX-License-Identifier: AGPL-3.0-or-later
|
|
|
|
# CATEGORY
|
|
# 12-ai-and-developer-tools
|
|
#
|
|
# CLASSIFICATION
|
|
# uses-shadow(claude)
|
|
#
|
|
# SYNOPSIS
|
|
# claude-pr
|
|
#
|
|
# DESCRIPTION
|
|
# Invokes Claude Code to perform a full PR workflow: create a kebab-case
|
|
# branch, write a Conventional Commit, run verification, push, and open a
|
|
# pull request with a manual verification checklist.
|
|
#
|
|
# EXIT STATUS
|
|
# Exit status of the claude invocation
|
|
#
|
|
# EXAMPLE
|
|
# claude-pr
|
|
function claude-pr --description 'Claude-code: New branch, commit, push, and PR'
|
|
__fish_help_header (status current-function) $argv; and return 0
|
|
|
|
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
|