Skip to content

feat(aidd-fix): add PageSpace MCP task status integration #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2witstudios wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(aidd-fix): add PageSpace MCP task status integration #213

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions ai/skills/aidd-fix/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,16 @@ Constraints {
## Step 1 — Gain Context and Validate
gainContext(bugReport | reviewFeedback) => confirmedIssue | stop {
1. Read the relevant source file(s) and colocated test file(s)
2. Read the task epic in `$projectRoot/tasks/` that covers this area
3. Reproduce or reason through the issue to confirm it exists
4. no change needed => summarize findings; stop — do not modify any files
2. Read the task that covers this area — from the PageSpace epic TASK_LIST if the `mcp__pagespace__*` tools are connected (read_page), otherwise the epic in `$projectRoot/tasks/`
3. PageSpace available => set the task to in_progress (update_task) once the issue is confirmed
4. Reproduce or reason through the issue to confirm it exists
Comment on lines +36 to +37

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Move the status update after issue confirmation

Because this skill requires steps to execute in order, PageSpace's update_task runs before step 4 confirms the issue. For a false or already-resolved bug report, step 5 then stops the workflow without restoring the status, leaving the task incorrectly marked in_progress. Reproduce or reason through the issue before updating its status.

Useful? React with 👍 / 👎.

5. no change needed => summarize findings; stop — do not modify any files
}

## Step 2 — Document the Requirement in the Epic
documentRequirement(confirmedIssue) => requirement {
1. Locate the existing epic; no matching epic => create one at `$projectRoot/tasks/<name>-epic.md` using /task
2. Add a requirement in **"Given X, should Y"** format describing the correct observable behavior
1. Locate the existing epic/task; none => create one with /task (a PageSpace TASK_LIST when the MCP tools are connected, else `$projectRoot/tasks/<name>-epic.md`)

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a PageSpace-aware path to create the task

When PageSpace is connected and no task exists, /task cannot provide the promised TASK_LIST: ai/skills/aidd-task-creator/SKILL.md:10 explicitly stores tasks under $projectRoot/tasks, and that skill contains no PageSpace branch. This creates a filesystem epic while subsequent steps attempt update_task against a nonexistent PageSpace task, so the new integration fails for exactly the missing-task case. Invoke the appropriate PageSpace creation operation here or add PageSpace support to /task first.

Useful? React with 👍 / 👎.

2. Add a requirement in **"Given X, should Y"** format describing the correct observable behavior — in the task's note (PageSpace) or the epic file
3. Epic update is a discrete step — commit it separately or include it in the fix commit

epicConstraints {
Expand Down Expand Up @@ -83,6 +84,7 @@ commitAndPush(reviewedFix) {
1. Stage only the files changed by this fix
2. Write a conventional commit message (e.g. `type(optional-scope): description`)
3. Run `git push -u origin <branch-name>`
4. PageSpace available => set the task to completed (update_task) and capture the root cause + the rule that prevents recurrence into PageSpace memory (a note page + a Memory Index line; do not grow the drive context for this)
}

fix = gainContext |> documentRequirement |> writeFailingTest |> implementFix |> selfReviewAndTest |> commitAndPush
Expand Down
Loading