Results for “git-hooks”

Audits a project's developer experience by scoring devcontainer, git hooks, linting, build caching, environment setup, and release pipeline, then generates a DX health report with prioritized recommendations.

Performs core GitHub operations such as authentication status checks, repository creation, cloning, forking, and managing issues and pull requests using the GitHub CLI.

Handles git and GitHub operations using the gh CLI, triggered by any github.com URL. Covers creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology.

Detect and prevent hardcoded secrets in git repositories using Gitleaks, including pre-commit hooks, CI/CD integration, custom rules, baseline management, and remediation workflows.

Manage GitHub repositories end-to-end: clone, create, fork, configure settings, protect branches, set secrets, create releases, and run workflows using gh or git+curl.

Sets up GitHub authentication for git and gh CLI, covering HTTPS tokens, SSH keys, and API access.

Manages a local GitHub knowledge base and searches GitHub via the gh CLI, covering repos, issues, and pull requests.

Executes GitHub CLI and git commands with proper authentication, enforcing the --repo flag and providing helper functions for code review comments with suggestion blocks.

GitHub 仓库操作、自动化与管理。使用 gh CLI 进行问题分类、PR 管理、CI/CD 操作、发布管理和安全监控。当用户想要管理 GitHub 问题、PR、CI 状态、发布、贡献者、过期项目或任何超出简单 git 命令的 GitHub 操作任务时使用。

Authenticates to GitHub using a token, SSH key, or the gh CLI, with guidance for troubleshooting common auth failures.

Interact with GitHub repositories using the gh CLI to check pull request status, list workflow runs, view logs, and query the GitHub API with JSON output.

Manage GitHub repositories: triage issues, review PRs, debug CI/CD, prepare releases, and monitor security alerts using the gh CLI.

Produces an evidence-backed inventory of live automations (jobs, hooks, connectors, MCP servers, wrappers) and recommends keep/merge/cut/fix-next actions before rewriting anything.

Runs a two-wave validation pipeline (deterministic checks then rule-based checks) before every git commit, writing a sentinel file that a pre-commit hook enforces. Includes optional quick mode (first wave only) and a fix loop with up to three iterations.

Set up pre-commit hooks on a Python project — standard file-hygiene checks plus a security gate (gitleaks secret scanning, Trivy filesystem scan for CVEs/secrets/misconfigs, and Bandit Python SAST). Use this whenever the user wants to add, configure, or fix pre-commit hooks on a Python repo, mentions .pre-commit-config.yaml, wants secret/vulnerability/SAST scanning on commits, or is setting up code-quality guardrails — even if they just say 'add pre-commit hooks' without naming the tools. Especially for uv-based GenAI/LLM backends. Handles the setup gotchas that break first-time installs: the Trivy binary, the required data/html.tpl report template, bandit[toml] + [tool.bandit] config, and the right .gitignore entries.

Detects drift between declared reality (docs, manifests, inventories, ADRs) and actual reality (filesystem, git state, dependencies, hooks) on session start, reporting findings with severity and evidence.