.claude/skills/sync-issue/SKILL.md
Sync a local task file to GitHub Issues in gdp-admin/SRE-task. Creates if issue is null, updates if set. Supports comments and PR attachment. Trigger on "push issue", "update issue", "sync issue", "create issue".
npx skillsauth add diziassyafadi/Manager sync-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Sync a task file to GitHub Issues. Auto-detects create (issue: null) vs update (issue set).
Argument: $ARGUMENTS — parse for these optional parts:
<filename> — task file to sync (without tasks/ prefix)comment: <text> — post a comment on the issuepr: <url_or_number> — attach a PR as "Resolved by" comment.claude/.claude-memory.md; stop if none foundpython3 .claude/skills/sync-issue/scripts/parse_task_file.py tasks/<filename>
Outputs JSON: title, status, due, issue, parent, type, state, body, filename.
If issue is null (new issue), also run: .claude/scripts/validate-task.sh tasks/<filename> — stop on failure.
Read .claude/.env for GITHUB_ISSUE_ASSIGNEES.
Create (issue is null) → mcp__github__issue_write method create:
owner=gdp-admin, repo=SRE-task, title, body, type from JSON, assignees from env.
Then write issue: <number> back to the task file frontmatter.
Update (issue is set) → mcp__github__issue_write method update:
Same fields + issue_number + state from JSON.
If status=done, also set completed: <today> in task file frontmatter.
python3 .claude/skills/sync-issue/scripts/sync_project.py <issue_number> <status> [--due <date>] [--parent <issue_number>]
Syncs to GitHub Projects v2: status, due date, and parent field (if configured in config JSON).
If organizing via GitHub issue links (separate from Projects field sync):
Use node_id from step 3 output.
mcp__github__sub_issue_write method add: owner=gdp-admin, repo=SRE-task, issue_number=<parent>, sub_issue_id=<node_id>, replace_parent=true.
comment: in args)mcp__github__add_issue_comment: owner=gdp-admin, repo=SRE-task, issue_number, body=comment text.
pr: in args)Full URL → use as-is. Number only → ask Dizi for full URL.
mcp__github__add_issue_comment body: Resolved by: [PR #<N>](<url>)
✓ Issue #<N> <created|updated> → https://github.com/gdp-admin/SRE-task/issues/<N>
↳ Project: Status=<status>, Due=<due or "not set">, Parent=<parent or "not set">
↳ Comment posted ← if applicable
↳ PR attached: <url> ← if applicable
development
Generate a weekly work report from local task files in a standard format. Trigger when Dizi says "weekly report", "generate weekly report", "weekly recap", or "what did I do this week".
development
Create a new task file in `tasks/` by collecting information from Dizi interactively. Trigger when Dizi says "new task", "create task", "add task", or wants to log a piece of work.
tools
Imports a GitHub Issue into a local task file in tasks/. Triggers when Dizi says "import issue", "pull issue from GitHub", "create local task from issue", provides a GitHub issue number, URL, or assignee username.
documentation
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]