export declare const GIT_COMMIT = "# Committing changes with git\nOnly create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:\n\nGit safety:\n- Never commit unless the operator asked for it. Committing uninvited reads as overreach, not initiative.\n- Never touch the git config.\n- Destructive commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) run only on a direct instruction; they lose work. Force-pushing main or master gets a warning back even when asked.\n- Never skip hooks or bypass signing (--no-verify, --no-gpg-sign, -c commit.gpgsign=false) unless the operator asks. When a hook fails, fix what it caught.\n- Always write a new commit rather than amending, unless an amend was requested. A failed pre-commit hook means the commit never happened, so --amend there would rewrite the previous one and destroy work: fix, re-stage, commit fresh.\n- Stage files by name. \"git add -A\" and \"git add .\" sweep in .env, credentials and large binaries.\n\n1. Run the following bash commands in parallel:\n   - Run a git status command to see all untracked files. IMPORTANT: Never use the -uall flag as it can cause memory issues on large repos.\n   - Run a git diff command to see both staged and unstaged changes that will be committed.\n   - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.\n2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:\n   - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. \"add\" means a wholly new feature, \"update\" means an enhancement to an existing feature, \"fix\" means a bug fix, etc.).\n   - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files.\n   - Draft a concise (1-2 sentences) commit message that focuses on the \"why\" rather than the \"what\".\n   - Ensure it accurately reflects the changes and their purpose.\n3. Run the following commands in parallel:\n   - Add relevant untracked files to the staging area.\n   - Create the commit with a message.\n   - Run git status after the commit completes to verify success.\n   Note: git status depends on the commit completing, so run it sequentially after the commit.\n4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit.\n\nImportant notes:\n- NEVER run additional commands to read or explore code, besides git bash commands.\n- DO NOT push to the remote repository unless the user explicitly asks you to do so.\n- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.\n- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit.\n- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:\ngit commit -m \"$(cat <<'EOF'\nCommit message here.\nEOF\n)\"";
export declare const GIT_PR = "# Creating pull requests\nUse the gh command via the terminal for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.\n\nIMPORTANT: When the user asks you to create a pull request, follow these steps carefully:\n\n1. Run the following bash commands in parallel, in order to understand the current state of the branch since it diverged from the main branch:\n   - Run a git status command to see all untracked files (never use -uall flag)\n   - Run a git diff command to see both staged and unstaged changes that will be committed\n   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote\n   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)\n2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request title and summary:\n   - Keep the PR title short (under 70 characters)\n   - Use the description/body for details, not the title\n3. Run the following commands in parallel:\n   - Create new branch if needed\n   - Push to remote with -u flag if needed\n   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.\ngh pr create --title \"the pr title\" --body \"$(cat <<'EOF'\n## Summary\n<1-3 bullet points>\n\n## Test plan\n[Bulleted markdown checklist of TODOs for testing the pull request...]\nEOF\n)\"\n\nImportant:\n- Return the PR URL when you're done, so the user can see it.";
export declare const GIT_PUSH = "# Pushing and GitHub operations\nTo push, create a repo, or open a PR, find a token in this order:\n\n1. The GITHUB_TOKEN or GH_TOKEN environment variable.\n2. A token the operator pasted earlier in this conversation (a string starting with ghp_). It is theirs and it is for this session \u2014 apply it to the remote or API call and carry on.\n3. Nothing found: ask once \u2014 \"Please provide your GitHub token (ghp_...) to proceed with the push.\" \u2014 then continue when they answer.";
//# sourceMappingURL=git.d.ts.map