القائمة
Orchestrates issue-driven agent loops that post cycle status to issue threads and incorporate human feedback in each cycle.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/jmagly/aiwg --skill issue-driven-alيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
WCAG accessibility analysis for color palettes including contrast ratios, compliance checking, and remediation suggestions. Use when user needs to verify colors meet accessibility standards.
Generate, analyze, compare, export, and suggest color palettes using color theory. Use when user asks about colors, palettes, color schemes, or needs help choosing colors for a project.
Research current color trends from Pantone, architecture, film, and design. Use when user asks about trending colors, popular palettes, or wants research-backed color inspiration.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| namespace | aiwg |
| name | issue-driven-al |
| description | Orchestrates issue-driven agent loops that post cycle status to issue threads and incorporate human feedback in each cycle. |
| platforms | ["all"] |
| requires | [{"issue":"issue number or URL to work on in the loop"},{"work":"description of the work to perform each cycle (the actual task — bug fix, feature, doc update)"}] |
| ensures | [{"cycle-status":"structured status comment posted to issue thread after every cycle"},{"thread-scan":"all human comments classified and incorporated into subsequent cycles"},"if resolved: completion summary comment posted with checklist confirmation"] |
| errors | [{"tracker-unavailable":"cannot read or post comments to issue tracker"},{"max-cycles-reached":"issue not resolved within cycle limit; escalation comment posted"}] |
| invariants | ["every cycle posts a status comment before returning, even partial cycles","human feedback from any cycle is always acknowledged in the next status comment","completion is only declared when all issue acceptance criteria are met"] |
Skill access pattern (post-kernel-pivot, 2026.5+)
Skill names referenced in this document are AIWG skills, not slash commands. Most are not kernel-listed and cannot be invoked as
/skill-nameby the platform. Reach them via:aiwg discover "<capability>" aiwg show skill <name>Only kernel-listed skills (
aiwg-doctor,aiwg-refresh,aiwg-status,aiwg-help,use,steward) are directly invokable as slash commands. See skill-discovery rule.
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
Transforms the issue tracker from a passive record into an active 2-way collaboration surface. Each Al cycle posts structured status to the issue thread, scans for human feedback, and responds substantively. The human can monitor and steer agent work asynchronously by commenting on the issue.
When triggered, this skill invokes the address-issues command with appropriate parameters extracted from the user's natural language request.
| User Says | Extracted Parameters |
|---|---|
| "address issues 17 18 19" | 17 18 19 |
| "fix open bugs" | --filter "status:open label:bug" |
| "work on the bug backlog" | --filter "status:open label:bug" |
| "tackle issue 17" | 17 |
| "go through all open issues" | --all-open |
| "address the open issues interactively" | --all-open --interactive |
| "focus on security bugs" |
--all-open --guidance "Focus on security bugs"| "fix bugs 17-19, they're all auth related" | 17 18 19 --guidance "These are all related to auth" |
This skill supports the standard AIWG --interactive and --guidance parameters:
--interactive: When detected in user intent (e.g., "interactively", "walk me through"), adds --interactive to invoke discovery questions before starting and pause between issues for human go/no-go.
--guidance: When the user provides upfront direction (e.g., "focus on bugs", "skip feature requests", "security first"), extracts the guidance text and passes it via --guidance "..." to tailor prioritization and approach without interactive prompts.
address-issues with extracted parametersEach cycle of the agent loop follows this protocol:
Step 1: Work — Read issue context, implement fix/feature, run tests
Step 2: Post Status — Post structured comment to the issue thread:
**AL CYCLE #N – [Progress|Blocked|Review Needed]**
- Actions taken this cycle
- Task checklist (updated)
- Blockers (if any)
- Next steps
Step 3: Scan & Respond — Read all new thread comments, classify them (feedback/question/approval/correction), and incorporate into the next cycle. Never ignore human input.
| Comment Type | Agent Response |
|---|---|
| Feedback | Incorporate into next cycle's work |
| Question | Answer in next status comment |
| Approval | Proceed to next phase or close issue |
| Correction | Adjust approach, acknowledge the change |
| Automated/bot | Ignore |
An issue is resolved when:
| Strategy | Trigger |
|---|---|
| Sequential | Default — one issue at a time |
| Batched | When user mentions "related" issues or same module |
| Parallel | When user says "in parallel" (respects context budget) |
Gitea (via MCP tools):
mcp__gitea__list_repo_issues — list issuesmcp__gitea__get_issue_by_index — read issuemcp__gitea__get_issue_comments_by_index — read threadmcp__gitea__create_issue_comment — post statusmcp__gitea__edit_issue — update labels/statusGitHub (via gh CLI):
gh issue list — list issuesgh issue view N — read issuegh issue comment N --body "..." — post statusgh issue close N — close resolved| Command | Integration |
|---|---|
ralph | Core loop engine |
issue-list | Fetches issues by filter |
issue-comment | Posts cycle status comments |
issue-close | Closes resolved issues |
issue-sync | Links commits to issues |
--max-cycles limit (default: 6)--interactive mode, pause between issues for human go/no-goDefault settings (overridable via parameters):
User: "tackle issue 17"
→ /address-issues 17
User: "work on the bug backlog"
→ /address-issues --filter "status:open label:bug"
User: "address issues 17, 18, 19 interactively"
→ /address-issues 17 18 19 --interactive
User: "go through all open issues, give each one up to 8 cycles"
→ /address-issues --all-open --max-cycles 8
User: "fix the open bugs, focus on security issues first"
→ /address-issues --filter "status:open label:bug" --guidance "Security issues are top priority"
User: "address issues 17, 18, 19 — they're all related to the auth refactor"
→ /address-issues 17 18 19 --guidance "These are all related to the auth refactor, address them as a batch"