Results for “git”

Deploy affiliate content to GitHub Pages for free hosting. Triggers on: "deploy to GitHub Pages", "host on GitHub Pages", "free hosting for my affiliate site", "push to GitHub Pages", "GitHub Pages setup", "deploy my landing page to GitHub", "host my bio link on GitHub", "free affiliate website hosting", "github pages affiliate", "set up GitHub Pages for my site", "deploy HTML to GitHub", "free static hosting", "publish my affiliate page for free", "github pages custom domain".

The English summary is being prepared. Showing the original description.

Manage GitHub issues and pull requests, proposed code changes, using the gh command-line tool. Create and inspect discussions, check automated test results, investigate failed logs, rerun jobs, and track authorized merges through to their verified status.

• Creating and updating issues or pull requests
• Checking pull request reviews and automated checks
• Investigating failed CI logs and rerunning jobs

Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.

• Starting feature work in a separate workspace
• Preparing a workspace before executing an implementation plan
• Checking whether a workspace is already isolated

Save, organize, synchronize, and retrieve documents, conversations, and project information across local files, memory tools, knowledge repositories, and databases. Check for duplicates before storing information and choose a suitable home for each type of knowledge.

• Saving documents and conversations to a knowledge base
• Consolidating duplicate notes
• Synchronizing knowledge across storage systems

Turn a vague request into a precise specification through five phases and file it as a GitHub issue. Optionally start a Claude Code agent in a separate working directory to begin implementation.

• Turn a rough idea into an actionable specification
• Create a GitHub issue from a request
• Convert a request into a backlog item

Build an HTML dashboard for a public GitHub repository, showing stars, forks, contributors, issues, pull requests, and recent activity. Choose a standalone page or source files that support updates and record where the data came from.

• Review a repository's activity in one dashboard
• Prepare an open-source project health report
• Check leading contributors and recent issues or pull requests

Investigate a GitHub project through repository data and web sources, then produce a Markdown report covering its development history, technical structure, activity metrics, and alternatives, with citations and diagrams where useful.

• Investigating an open source project's technical structure
• Reconstructing development milestones from commits and releases
• Comparing a project with competing alternatives

Manage GitHub pull requests from creation through review and merge. Using GitHub CLI, the skill prepares descriptions, coordinates reviewers, tracks automated checks, helps resolve conflicts, and selects merge approaches suited to the branch history.

• Create a feature pull request with a clear description
• Coordinate security, performance, and code quality reviews
• Enable auto-merge after tests pass

Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.

• Reviewing a backlog of open issues and pull requests
• Checking whether reported bugs are already fixed
• Assessing pull request readiness for merging

Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.

• Committing related changes in focused groups
• Reorganizing branch history with rebase or squash
• Tracing when and where code changed

Manage scientific datasets with DataLad and git-annex, which tracks large files separately from Git history. Retrieve selected data, record analysis commands and their inputs and outputs, rerun recorded work, and publish history alongside file content.

• Retrieve only the research data you need
• Resolve files that contain pointers instead of data
• Record and rerun analysis steps

Set up ArgoCD to keep Kubernetes deployments aligned with configuration stored in Git, an approach called GitOps. Follow guidance for multiple environments, automatic synchronization, deployment ordering, access permissions, and troubleshooting differences.

• Set up Kubernetes deployments driven by Git changes
• Manage staging and production configurations
• Configure synchronization order and pre-deployment jobs

Carry out an engineering plan through stepwise code changes, dependency impact checks, tests, and focused commits. It also handles small, bounded tasks directly, checking the code relationship index before relying on its results.

• Implementing an existing engineering plan
• Making a small change across one or two files
• Testing each step before committing

Set up CodeQL security scanning in GitHub Actions or with the local CLI. Get guidance on language settings, build steps, analysis rules, result uploads, and troubleshooting so you can configure scans and interpret their findings.

• Adding security scans to GitHub Actions
• Running local scans with the CodeQL CLI
• Investigating failed builds or result uploads

Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.

• Breaking feature requirements into GitHub Issues
• Mapping dependencies and setting work priorities
• Preparing sprint estimates and completion criteria

Manage Git branches, resolve conflicting changes, organize commit history, and recover earlier work after mistakes. Also helps teams choose a branching workflow that fits how they review changes, integrate work, and release software.

• Resolving conflicts during a merge or rebase
• Organizing commits before merging a branch
• Recovering deleted branches or older file versions

Prepare a separate Git working directory for feature development, then install project dependencies and run baseline tests. Check for existing isolation first, use native worktree tools when available, and otherwise fall back to Git.

• Starting feature development in a separate working directory
• Preparing a workspace before executing an implementation plan
• Reusing an existing isolated workspace

Manage Git worktrees, separate folders for working on different branches, with commands to create, list, and remove them. Move uncommitted changes between folders, copy environment files, and open a worktree in an editor.

• Working on a feature and a bug fix in separate folders
• Moving uncommitted changes to another worktree
• Applying stashed changes to a worktree

Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.

• Write commit messages using Conventional Commits
• Organize branches and Pull Request reviews
• Resolve conflicts during merge or rebase

Create readable GitHub Actions step summaries that put key results first. Organize headings, format code and review findings, and place lengthy logs or diagnostics in expandable sections for easier scanning.

• Making workflow results easier to scan
• Placing lengthy logs in expandable sections
• Organizing review findings by severity and action

Create GitHub Copilot coding tasks from plain-language instructions using the GitHub CLI extension. Tasks become issues that trigger code changes and pull requests for review, with commands to list tasks, inspect details, and update instructions.

• Delegate a bug fix to GitHub Copilot
• Create a task from a written specification
• List tasks and inspect their details

GitHub Actions の CI 失敗を調査するスキル。失敗した run / PR / job の URL（例: https://github.com/OWNER/REPO/actions/runs/RUNID、…/pull/PR、…/job/JOBID）や run_id・PR 番号を貼られて「このCIが失敗している、原因を調査して」「ビルド/テストがコケた、なぜ落ちたか調べて」「workflow が failed、修正案を出して」「job のログを見て」と頼まれたら必ず使う。WebFetch では github.com のログは取れない（PreToolUse hook が差し戻し、HTML しか返らない）ため、gh（`gh run view --log-failed` / `gh run view --job` / `gh pr checks` / `gh api`）で失敗ジョブ・ステップと失敗ステップのログだけを決定論スクリプトで収集し、失敗原因を特定して修正案を提示する。GitHub Actions 以外（GitLab CI 等）や、URL がログではなくソース閲覧目的のときは対象外。GitHub(gh) 前提。`/gh-ci-investigate` で明示起動も可。

The English summary is being prepared. Showing the original description.

Operate the ClawSweeper maintenance bot for OpenClaw issues and pull requests, which are proposed code changes. Read findings, create repair jobs, monitor GitHub Actions, and manage automatic fixes or merges subject to authorization and validation checks.

• Reviewing issue and pull request sweep reports
• Creating a repair job from an existing report
• Investigating failed GitHub Actions runs

Manage GitHub repository operations with the gh command-line tool. Classify issues, check pull request readiness, investigate failed automated checks, prepare releases and changelogs, and review dependency or exposed-secret security alerts.

• Classifying issues and finding duplicates
• Checking pull request reviews and merge readiness
• Investigating failed CI workflows