36 docs tagged with "GitHub"

As of October 4, 2026; inventory only, not content clearance or acceptance. Iceman examined the original build repository and locally registered worktrees on jkdev001, plus the non-Git incumbent controller directory. No original files, Git refs, services, or runtime code were changed. The project execution record is jknash/agent-orchestration story kanban/stories/AF-02.md; this report is the sanitized owner-review summary. A machine-readable, 157-row path/blob inventory and reproducible read-only scanner are prepared on work/AF-02/inventory-01, pending project publication and PM review.

Intent

Whole-repo code audits via Codex/Claude CLI agents.

Intent

Copy this into a story's action_needed or a handoff message when an agent

Triage GitHub repos for useful agent skills or MCP servers.

The complete procedure for the daily refresh of Justin's finance

Date: 2026-10-03. The approved integration of the stalled

Date review of the stalled jknash/personal-dashboard project, a

Date: 2026-10-04. Stakeholder-approved addition, executed by the finance

Date: 2026-10-04. Built and deployed by the finance agent

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

Use when merged worktrees retain local work. Recover safely.

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.

Review PRs: diffs, inline comments via gh or REST.

Carry a GitHub issue to a verified PR with honest CI state.

Create, triage, label, assign GitHub issues via gh or REST.

GitHub PR lifecycle: branch, commit, open, CI, merge.

Clone/create/fork repos; manage remotes, releases.

Three recent saved posts (two from @buildwithneej, one from @godofprompt) featured

Verify a GitHub token's access to a repo before clone/push.

Status: APPROVED (chief of staff, 2026-10-10) on the

Intent

A running list of open-source projects the owner flags as

Use when merging split code+issues+Kanban to one repo.

The fleet's repo-creation procedure. A new repository is not

Sync eligible Hermes skills to a shared git repo safely.

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Intent

Owner-approved 2026-10-08, built the same day by the finance desk

How to ship a change to Justin's personal workbench: the static site in the