skills.rest
mattjefferson
mattjeffersonCOMMUNITY
Explore all skills by this author →
Website𝕏@mjeffersonGitHub

he-github

Automate GitHub Pull Request lifecycle with consent gates and artifact linking.

4|1|Updated Feb 14, 2026
Search Tags:#automation#ci/cd#code review#pull request#github#consent
One-click install
npx skills add https://github.com/mattjefferson/harness-engineering --skill he-github
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: he-github
Source: https://github.com/mattjefferson/harness-engineering/tree/main/skills/he-github
Command: npx skills add https://github.com/mattjefferson/harness-engineering --skill he-github

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the GitHub Pull Request lifecycle, ensuring that code changes are reviewed, verified, and merged only after explicit consent and adherence to defined gates, preventing accidental merges or unauthorized pushes.

Core Features & Use Cases

  • PR Automation: Opens, updates, and manages GitHub Pull Requests using the gh CLI.
  • Consent Gates: Implements tiered consent for remote operations, requiring explicit approval for merges and force-pushes.
  • Evidence Linking: Ensures PRs link to relevant specifications, plans, and evidence artifacts.
  • CI Integration: Monitors and responds to CI check statuses.
  • Use Case: After completing an implementation task, use this Skill to automatically create a PR, link it to the project plan, and await review, ensuring all checks pass before a merge is even considered.

Quick Start

Use the he-github skill to open a pull request for the current branch, linking to the plan located at docs/plans/active/my-feature-plan.md.

Frequently Asked Questions about he-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull requests with required consent gates?▼

You can automate the GitHub pull request lifecycle by opening, updating, and merging PRs while enforcing explicit consent gates for remote operations to prevent unauthorized pushes.

What's the best way to link pull requests to project plans and specifications?▼

The best way to link pull requests to specifications is by using PR automation that automatically attaches canonical artifacts, ensuring code changes map directly to project plans and evidence.

How do I manage CI check statuses before merging a pull request?▼

You can manage CI check statuses by automating feedback loops within the pull request workflow, ensuring all CI checks pass before a merge is even considered.

Does this PR automation tool require the gh CLI to manage remote operations?▼

Yes, this PR automation tool relies on the gh CLI to open, update, and manage GitHub Pull Requests while maintaining safety invariants for remote operations.

Why do I need explicit approval for merging pull requests in an automated workflow?▼

Explicit approval for merging pull requests is required to prevent accidental merges or unauthorized pushes, enforcing tiered consent gates and adherence to defined project workflows.

Can I use this to open a pull request for the current branch and wait for review?▼

Yes, you can open a pull request for the current branch, link it to your project plan, and automatically await review while verifying that all checks pass before merging.

Related Skills

Explore More Software Engineering Skills→
tonombtonomb

setup-matt-pocock-skills

Configure issue trackers, triage labels, and documentation layouts across GitHub, GitLab, and local markdown.

Community
Intermediate
lvlup-swlvlup-sw
33

cleanup

Verify merged PRs, backfill metadata, and prune git worktrees and branches.

Official
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
cryptopaficryptopafi

github-issues

Manage and triage GitHub issues via CLI or REST API.

Community
Intermediate