Automate GitHub issue and PR operations with bot PAT authentication.
npx skills add https://github.com/happier-dev/happier --skill happier-github-ops
Please help me install this Agent Skill. Skill: happier-github-ops Source: https://github.com/happier-dev/happier/tree/main/skills/happier-github-ops Command: npx skills add https://github.com/happier-dev/happier --skill happier-github-ops
It solves the problem of reliably running GitHub operations as the Happier bot account without interactive authentication or accidental use of the wrong identity.
yarn ghops wraps gh and enforces using HAPPIER_GITHUB_BOT_TOKEN for bot-scoped actions.GH_PROMPT_DISABLED=1 and prevents running when the token is missing.GH_CONFIG_DIR by default to reduce side effects.roadmap, priority:p0), yarn ghops provides the consistent command surface.Run yarn ghops issue create -R happier-dev/happier --title "Report test failure" --body "Summary of what happened and expected behavior" --label "type: bug" after setting HAPPIER_GITHUB_BOT_TOKEN.
High-intent search queries and answers about installing and using this skill.
You can automate GitHub CLI operations by setting GH_PROMPT_DISABLED=1 and using an isolated GH_CONFIG_DIR to prevent interactive prompts and unintended configuration side effects during non-interactive execution.
The best way to create and label public roadmap issues in CI is by running an automated GitHub CLI operation that enforces a forced PAT authentication token. This ensures consistent identity and correct labels for issues and PRs.
You prevent your automated GitHub bot from using the wrong identity by forcing PAT authentication via a specific bot token environment variable. This guarantees operations execute strictly as the intended bot account.
Yes, running GitHub CLI commands in LLM-driven workflows requires an isolated configuration directory to reduce side effects. Using an isolated GH_CONFIG_DIR prevents unintended configuration changes during automated maintenance.
If the GitHub bot authentication token is missing during roadmap automation, the system prevents execution. This safety mechanism ensures automated GitHub CLI operations fail rather than running unauthenticated or with incorrect credentials.
Yes, you can use GitHub CLI to apply roadmap labels to issues and PRs for automated maintenance. The CLI provides a consistent command surface to correctly label public issues, such as adding roadmap or priority tags.
jonnymuirValidate CI/CD pipelines for semantic versioning, token security, and registry retry logic.
saitocoAutomate GitHub issue triage and metadata maintenance with JSON output.
giosuetedeschi-specAutomate GitHub repository management tasks including pull request reviews, issue triage, and CI/CD pipeline orchestration.
sparkfabrikAutomate GitHub workflow tasks using the gh CLI for issues, PRs, actions, releases, and repositories.