agent-flutter 0.1.23 → 0.1.24

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-flutter",
-  "version": "0.1.23",
+  "version": "0.1.24",
   "description": "Portable Flutter skill/rule pack initializer for multiple AI IDEs.",
   "type": "module",
   "bin": {

package/src/cli.js

@@ -724,6 +724,9 @@ When a task matches a skill, load the corresponding \`SKILL.md\` under:
 
 For new project scaffolding, run:
 \`bash .cursor/scripts/bootstrap_flutter_template.sh\`
+
+After finishing UI/API tasks, ask user in order:
+\`Commit now?\` -> \`Push now?\` -> \`Create PR now?\`
 `;
 }
 
@@ -737,7 +740,8 @@ Required order:
 2. If task matches a skill, load \`.windsurf/skills/<skill>/SKILL.md\`.
 3. For new project scaffolding, run \`bash .windsurf/scripts/bootstrap_flutter_template.sh\`.
 4. Keep spec documentation synchronized after UI/API changes.
-5. For completed UI/API features, follow \`.windsurf/rules/shared/ci-cd-pr.md\` before handoff.
+5. For completed UI/API features, follow \`.windsurf/rules/shared/ci-cd-pr.md\`.
+6. Ask user in order: \`Commit now?\` -> \`Push now?\` -> \`Create PR now?\`.
 `;
 }
 
@@ -752,7 +756,8 @@ Execution checklist:
 3. For new project scaffolding, run \`bash .clinerules/scripts/bootstrap_flutter_template.sh\`.
 4. Preserve Flutter architecture conventions and localization requirements.
 5. Update docs/specs after behavior changes.
-6. For completed UI/API features, follow \`.clinerules/rules/ci-cd-pr.md\` before handoff.
+6. For completed UI/API features, follow \`.clinerules/rules/ci-cd-pr.md\`.
+7. Ask user in order: \`Commit now?\` -> \`Push now?\` -> \`Create PR now?\`.
 `;
 }
 
@@ -767,7 +772,8 @@ Follow this order when generating code:
 3. For new project scaffolding, run \`bash .github/scripts/bootstrap_flutter_template.sh\`.
 4. Keep architecture, localization, and UI conventions aligned with local instructions.
 5. Update specs/docs when UI/API behavior changes.
-6. For completed UI/API features, follow \`.github/rules/ci-cd-pr.md\` before final handoff.
+6. For completed UI/API features, follow \`.github/rules/ci-cd-pr.md\`.
+7. Ask user in order: \`Commit now?\` -> \`Push now?\` -> \`Create PR now?\`.
 `;
 }
 

package/templates/shared/TEMPLATES.md

@@ -63,6 +63,9 @@ Use this after completing UI/API work to trigger CI/CD rule and PR creation:
 Finalize this feature:
 - Branch name: [e.g. feat/login-session-timeout]
 - Commit message: [e.g. feat(auth): handle session timeout]
+- Commit now?: [yes/no]
+- Push now?: [yes/no]
+- Create PR now?: [yes/no]
 - Base branch: [e.g. dev]
 - PR title: [e.g. feat(auth): handle session timeout]
 - Feature summary: [...]

package/templates/shared/rules/ci-cd-pr.md

@@ -15,9 +15,13 @@ This is the required "done" flow before feature handoff.
    - `fvm flutter analyze`
    - Run related tests for the changed scope (unit/widget/integration when available).
 2. Ensure spec/docs are updated if behavior changed.
-3. Commit with clear scope and summary.
-4. Push branch to remote.
-5. Create PR with mandatory template sections.
+3. Ask user explicitly: `Do you want me to commit now? (yes/no)`
+4. If answer is `yes`, create commit with clear scope and summary.
+5. Ask user explicitly: `Do you want me to push now? (yes/no)`
+6. If answer is `yes`, push branch to remote.
+7. Ask user explicitly: `Do you want me to create PR now? (yes/no)`
+8. If answer is `yes`, create PR with mandatory template sections.
+9. If any answer is `no`, stop at that step and return current status.
 
 If any step is skipped, feature is not considered complete.
 
@@ -43,5 +47,7 @@ PR must follow `.github/pull_request_template.md` and include all sections:
 - Branch protection must require this check before merge.
 
 ## 6. Agent Behavior
-- After finishing UI/API tasks, agent must complete commit + push + PR creation.
-- Agent should return PR URL as final output for the task.
+- After finishing UI/API tasks, agent must ask in order: commit -> push -> create PR.
+- Agent must execute only steps explicitly confirmed by user (`yes`).
+- If user confirms all steps, agent returns PR URL as final output.
+- If user declines at any step, agent stops and returns current repository status.