Search skills.../

Project Board Sync | Skills Pool

Skill File

Project Board Sync

Keep GitHub Project 15 board status synchronized while implementing issues. USE WHEN user asks to start implementation, work an issue, create sub-issues, move issue status, or keep Board current during coding.

anarchitects0 starsMar 24, 2026

Occupation
Categories: Git Workflows

Skill Content

Use this skill during issue-driven implementation to keep the planning board aligned with actual execution.

Target Project

Project: https://github.com/orgs/anarchitects/projects/15
Owner: anarchitects
Number: 15
Working view: Board
Sprint field: Milestone
Status options: Backlog, Todo, In Progress, In Review, Blocked, Done

Required Workflow

At implementation start:

Set active parent issue and active sub-issues to In Progress.

During execution:

Set Blocked immediately when work cannot proceed.
Keep active and inactive issues separated.
Keep Milestone and Priority unchanged unless user asks to modify them.

Review handoff:

Related Skills

Quick Install

Project Board Sync

npx skills add anarchitects/anarchitecture-bricks-3tier

Download Skill Open repository

Author: anarchitects
stars: 0
Updated: Mar 24, 2026
Occupation

On this page

01Target Project

Set issue to In Review when implementation is complete and review is requested or a PR is opened.

Completion:

Set Done only after completion criteria are met.

Common Board Operations

Read fields:

gh project field-list 15 --owner anarchitects --format json

Read project items:

gh project item-list 15 --owner anarchitects --format json

Edit one field value on one item:

gh project item-edit --id <item-id> --project-id <project-id> --field-id <field-id> --single-select-option-id <option-id>

Add issue to project:

gh project item-add 15 --owner anarchitects --url https://github.com/anarchitects/anarchitecture-bricks-3tier/issues/<issue-number>

Status Mapping Guidance

Backlog: prioritized but not selected for active execution.
Todo: selected for active sprint but not started.
In Progress: currently being implemented.
In Review: implementation ready for review or PR stage.
Blocked: waiting for dependency, decision, or environment fix.
Done: accepted and complete.

Safety Rules

Use non-interactive gh commands.
Verify updates with a read-after-write query.
Avoid bulk overwrites without issue number filters.
Report changed issue numbers and resulting statuses in the final response.

Human In The Loop Rules

Treat board updates as AI-assisted planning operations under human supervision.
Human developers review code, perform commits, create PRs, and merge PRs.
AI coding agents may suggest commit messages, but commit execution remains human-owned.
When implementation changes may be breaking, explicitly call that out in updates and summaries.
When bug-fix impact suggests package deprecation on npm, explicitly call this out and require explicit human approval before any deprecation execution.

02

Required Workflow

03Common Board Operations

04Status Mapping Guidance

06Human In The Loop Rules

Project Management Specialists

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Author Contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft184.0k

Repository Setup

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.

Significant-Gravitas183.5k

Project Management Specialists