Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
83 commits
Select commit Hold shift + click to select a range
31e5b4b
feat(vcs): Add git workflow for VCS abstraction
Jan 20, 2026
77dba6b
refactor(setup): Decouple VCS logic from project inception
Jan 20, 2026
1d9cbba
refactor(setup): Abstract VCS-specific file listing
Jan 20, 2026
493ff82
refactor(revert): Decouple revert logic from Git
Jan 20, 2026
e7fcbb1
refactor(vcs): Replace git notes with VCS-agnostic metadata log
Jan 20, 2026
d81bc79
feat(revert): Enhance revert plan with detailed commit summaries
Jan 20, 2026
58a3617
fix(conductor): Create and update metadata log
Jan 20, 2026
66101e9
fix(vcs): Implement safe JSONL logging for metadata
Jan 21, 2026
6dffea0
feat(vcs): Enhance git.md with structured error handling
Jan 21, 2026
9dab75f
refactor(conductor): Use get_commit_metadata command
Jan 21, 2026
3643399
feat(conductor): migrate interactive prompts to AskUser tool
jerop Jan 29, 2026
cd3e374
chore(conductor): rename AskUser tool to ask_user
jerop Jan 29, 2026
fef5dd2
feat(conductor): use ask_user tool in review command
jerop Jan 29, 2026
a40d66f
chore(conductor): Add post-execution advice to commands
sherzat3 Jan 30, 2026
b1609bb
feat: Conductor 0.2.0 - Unified Core & Multi-Platform Integration
edithatogo Feb 1, 2026
497a143
tmp, mcp
Jan 27, 2026
46bb756
refactor to make it easier to add future vcs
Jan 28, 2026
7af30ce
tmp - finishing up mcp
Feb 3, 2026
d020bf3
finished jj/git abstraction
Feb 3, 2026
6e3f1ec
mcp done
Feb 3, 2026
121b06c
feat(vcs): add revert, log filtering, and robustness improvements
Feb 3, 2026
4e85149
change command prompting
Feb 3, 2026
ea2e8e2
feat(implement): add ralph mode loop
moisgobg Jan 27, 2026
c337c49
feat(ralph): refactor autonomous loop to MCP-based AfterTool hooks
moisgobg Jan 29, 2026
14068e5
chore(conductor): Ensure Ralph state file is ignored in VCS
moisgobg Jan 29, 2026
63a3c52
refactor(ralph): Move directive to Markdown and use relative path res…
moisgobg Jan 30, 2026
b843867
feat(ralph): Pivot to Architect Mode (Plan Refinement Loop)
moisgobg Jan 31, 2026
475ec8a
feat(templates): add GCP best practices guide
hminooei Feb 5, 2026
d8b0574
feat(templates): update GCP best practices with IaC and IAM checks
hminooei Feb 6, 2026
75d99cf
chore(main): release conductor 0.3.0
google-conductor-bot Feb 6, 2026
35cdde5
feat(conductor): Add GCP best practices template and integration logic
hminooei Feb 6, 2026
abfbc3b
refactor(conductor): Rename '2.4_code_styleguides' to '2.4_project_gu…
hminooei Feb 9, 2026
26a2330
feat(conductor): Add platform_guides check to review.toml
hminooei Feb 9, 2026
3c388fa
refactor(conductor): Rename 'Style Compliance' to 'Guides Compliance'…
hminooei Feb 9, 2026
f2b7ba5
fix(conductor): move pre-initialization overview before resume check
Feb 9, 2026
c26980a
feat(conductor): update review process to commit fixes and update plan
Feb 9, 2026
57055df
feat(conductor): migrate interactive prompts to `AskUser` tool
moisgobg Feb 9, 2026
27c79fd
refactor(conductor): Split Code Style and Platform Guides into distin…
hminooei Feb 10, 2026
2eec7ef
feat(conductor): Refine checks and transitions for platform guides
hminooei Feb 10, 2026
db0e367
refactor(conductor): Add Product Guidelines check to review.toml
hminooei Feb 10, 2026
4eb56d8
fix(conductor): Correct section reference in setup.toml resume logic
hminooei Feb 10, 2026
dda8407
Merge remote-tracking branch 'upstream/main'
edithatogo Feb 10, 2026
0c6cddd
Merge remote-tracking branch 'upstream/chore/add-post-execution-tips'
edithatogo Feb 10, 2026
03975f2
Merge remote-tracking branch 'upstream/feat/add-gcp-template'
edithatogo Feb 10, 2026
4b24ddb
Merge remote-tracking branch 'upstream/feat/ask-user-tool-integration'
edithatogo Feb 10, 2026
82c2afa
Merge remote-tracking branch 'upstream/feat/ralph-loop'
edithatogo Feb 10, 2026
f657f54
Merge remote-tracking branch 'upstream/feat/use-ask-user-tool'
edithatogo Feb 10, 2026
89beda8
Merge remote-tracking branch 'upstream/fix/review-commit'
edithatogo Feb 10, 2026
d1960ec
Merge remote-tracking branch 'upstream/fix/setup'
edithatogo Feb 10, 2026
2269b2a
Merge remote-tracking branch 'upstream/release-please--branches--main…
edithatogo Feb 10, 2026
8ec6526
Merge remote-tracking branch 'upstream/vcs-support'
edithatogo Feb 10, 2026
c7c83a0
Merge remote-tracking branch 'upstream/vcs-support-mcp'
edithatogo Feb 10, 2026
d9c4659
chore(sync): Update platform-specific artifacts and skill definitions
edithatogo Feb 10, 2026
48a8b1a
chore(sync): Bundle full instructions into all SKILL.md files and add…
edithatogo Feb 10, 2026
9c8f39d
chore(conductor): Implement maintenance and synchronization improvements
edithatogo Feb 10, 2026
45496f3
chore(conductor): Archive maintenance track
edithatogo Feb 10, 2026
5aa329f
feat(repo): Implement Repository Excellence track (Phase 1-3)
edithatogo Feb 10, 2026
8d1c84d
chore(sync): Final platform synchronization after infrastructure upgrade
edithatogo Feb 10, 2026
09a466f
feat: implement universal installer, upstream sync bot, and documenta…
edithatogo Feb 14, 2026
859211f
fix: address review findings and add tests/docs
edithatogo Feb 14, 2026
58cf0e2
Standardize skill installation and distribution across agentic tools
edithatogo Feb 14, 2026
2da2fe3
feat: implement universal installer with marketplace integration and …
edithatogo Feb 15, 2026
0308285
feat(phase2): Complete Phase 2 - Tool Configuration [3a8f9b2]
edithatogo Feb 23, 2026
44c1715
chore(pre-commit): exclude validate_docs.py from ruff, ignore T201 pr…
edithatogo Feb 23, 2026
fb5c64e
docs(track): Complete documentation_standards_20260214 track - all 6 …
edithatogo Feb 23, 2026
fffd960
chore: archive documentation_standards_20260214 track [fb5c64e]
edithatogo Feb 23, 2026
3f0b5e3
feat: create sync_upstream.py for upstream repository sync
edithatogo Feb 23, 2026
88411a1
feat: add upstream sync bot with issue triage and GitHub Actions
edithatogo Feb 23, 2026
13aa86c
docs: mark Phases 1-3 complete for upstream_sync_bot_20260214
edithatogo Feb 23, 2026
95fbc7f
feat: complete Phase 4 - Repository Rename Coordination
edithatogo Feb 23, 2026
a863c25
docs: mark Phase 4 complete - Repository Rename Coordination [95fbc7f]
edithatogo Feb 23, 2026
16135e7
feat: Phase 5 - Create 8 tracks from upstream issues
edithatogo Feb 23, 2026
d4ed2c5
docs: mark upstream_sync_bot_20260214 COMPLETE - all 6 phases done [1…
edithatogo Feb 23, 2026
03357ba
chore: archive upstream_sync_bot_20260214, add 8 new issue tracks
edithatogo Feb 23, 2026
484b7df
feat: Phase 1 & 2 - AskUser tool integration for issue #105
edithatogo Feb 23, 2026
6fe2d5d
feat: Phase 3 - Migrate conductor-revert to AskUser tool
edithatogo Feb 23, 2026
5df9ec2
docs: Mark issue_105_20260223 COMPLETE - AskUser integration done [6f…
edithatogo Feb 23, 2026
344daff
chore: Archive issue_105 (AskUser), start issue_113 (.gitignore)
edithatogo Feb 23, 2026
183ccc0
feat: issue_113 - Auto-create .gitignore for tracks
edithatogo Feb 23, 2026
0ca1faf
docs: Mark issue_113 COMPLETE - .gitignore auto-creation done [183ccc0]
edithatogo Feb 23, 2026
bb8be9d
chore: Archive issue_113, start issue_112
edithatogo Feb 23, 2026
d5cdf7f
feat: Batch complete remaining tracks (issue_112, 115, 108, 103, 97, 96)
edithatogo Feb 23, 2026
51370d2
docs: Final tracks summary - All 13 tracks complete!
edithatogo Feb 23, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
19 changes: 19 additions & 0 deletions .devcontainer/Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
FROM mcr.microsoft.com/devcontainers/python:3.12-bookworm

# Install Node.js
RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - &&
apt-get install -y nodejs

# Install Mamba (via Micromamba)
RUN curl -Ls https://micro.mamba.pm/api/micromamba/linux-64/latest | tar -xj bin/micromamba &&
mv bin/micromamba /usr/local/bin/micromamba &&
micromamba shell init -s bash -p /opt/conda &&
/usr/local/bin/micromamba install -y -n base -c conda-forge mamba

# Setup environment
COPY environment.yml /tmp/environment.yml
RUN mamba env update -n base -f /tmp/environment.yml &&
rm /tmp/environment.yml

# Install VS Code extension development tools
RUN npm install -g @vscode/vsce typescript
19 changes: 19 additions & 0 deletions .devcontainer/devcontainer.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"name": "Conductor Dev Environment",
"build": {
"dockerfile": "Dockerfile",
"context": ".."
},
"customizations": {
"vscode": {
"extensions": [
"ms-python.python",
"ms-python.vscode-pylance",
"charliermarsh.ruff",
"ms-python.mypy-vscode",
"dbaeumer.vscode-eslint"
]
}
},
"remoteUser": "vscode"
}
1 change: 1 addition & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
*.md text eol=lf
33 changes: 33 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
name: Bug Report
description: Report a bug or unexpected behavior
title: '[Bug]: '
labels: ['bug', 'triage']
assignees: []
---

## Description
<!-- A clear and concise description of what the bug is. -->

## To Reproduce
Steps to reproduce the behavior:
1. Run command '...'
2. See error

## Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->

## Actual Behavior
<!-- What actually happened, including any error messages or logs. -->

## Environment
- OS: [e.g., Windows 11, macOS 14, Ubuntu 22.04]
- Python version: [e.g., 3.12]
- Conductor version: [e.g., 0.2.0]
- AI Tool: [e.g., Gemini CLI, Claude Code, VS Code]

## Additional Context
<!-- Add any other context about the problem here, including logs or screenshots. -->

## Possible Solution
<!-- If you have suggestions on a fix for the bug. -->
72 changes: 72 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
name: Bug Report
description: Report a bug in conductor-next
title: "[BUG] "
labels: ["bug"]
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to report a bug!

- type: textarea
id: description
attributes:
label: Description
description: A clear and concise description of the bug
placeholder: When I try to...
validations:
required: true

- type: textarea
id: reproduce
attributes:
label: Steps to Reproduce
description: Steps to reproduce the behavior
placeholder: |
1. Run command '...'
2. See error
validations:
required: true

- type: textarea
id: expected
attributes:
label: Expected Behavior
description: What you expected to happen
validations:
required: true

- type: textarea
id: actual
attributes:
label: Actual Behavior
description: What actually happened
validations:
required: true

- type: input
id: version
attributes:
label: Version
description: What version of conductor are you using?
placeholder: e.g., 0.2.0
validations:
required: true

- type: dropdown
id: os
attributes:
label: Operating System
options:
- macOS
- Linux
- Windows
- Other
validations:
required: true

- type: textarea
id: additional
attributes:
label: Additional Context
description: Add any other context about the problem
30 changes: 30 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
name: Feature Request
description: Suggest an idea for this project
title: '[Feature]: '
labels: ['enhancement', 'triage']
assignees: []
---

## Problem Statement
<!-- Is your feature request related to a problem? Please describe. -->
<!-- Example: "I'm always frustrated when..." -->

## Proposed Solution
<!-- A clear and concise description of what you want to happen. -->

## Alternative Solutions
<!-- A clear and concise description of any alternative solutions or features you've considered. -->

## Use Cases
<!-- Describe specific use cases where this feature would be valuable. -->
<!-- Example workflows or scenarios that would benefit from this feature. -->

## Implementation Ideas
<!-- If you have ideas about how this feature could be implemented, share them here. -->

## Additional Context
<!-- Add any other context, mockups, or examples about the feature request here. -->

## References
<!-- Link to related issues, discussions, or external resources. -->
48 changes: 48 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
name: Feature Request
description: Suggest a new feature for conductor-next
title: "[FEATURE] "
labels: ["feature"]
body:
- type: markdown
attributes:
value: |
Thanks for suggesting a new feature!

- type: textarea
id: description
attributes:
label: Description
description: A clear and concise description of the feature
placeholder: I would like to be able to...
validations:
required: true

- type: textarea
id: problem
attributes:
label: Problem Statement
description: What problem does this feature solve?
validations:
required: true

- type: textarea
id: solution
attributes:
label: Proposed Solution
description: Describe the solution you'd like
validations:
required: true

- type: textarea
id: alternatives
attributes:
label: Alternatives Considered
description: Describe any alternative solutions you've considered
validations:
required: false

- type: textarea
id: additional
attributes:
label: Additional Context
description: Add any other context or screenshots
49 changes: 49 additions & 0 deletions .github/ISSUE_TEMPLATE/upstream_sync.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
---
name: Upstream Sync Issue
description: Report an issue with upstream repository synchronization
title: '[Sync]: '
labels: ['upstream-sync', 'triage']
assignees: []
---

## Upstream Repository
<!-- Which upstream repository is this about? -->
- [ ] gemini-cli-extensions/conductor
- [ ] jnorthrup/conductor2
- [ ] Other: ___________

## Issue Type
<!-- What kind of sync issue is this? -->
- [ ] Merge conflict detected
- [ ] Sync failed
- [ ] Missing upstream changes
- [ ] Incorrect branch comparison
- [ ] Other: ___________

## Description
<!-- Describe the sync issue in detail. -->

## Sync Run Details
<!-- If applicable, provide details from the sync run. -->
- Sync timestamp:
- Upstream commit SHA:
- Error message (if any):

## Expected Behavior
<!-- What should have happened during the sync? -->

## Actual Behavior
<!-- What actually happened? -->

## Suggested Action
<!-- What should be done to resolve this? -->
- [ ] Create manual PR
- [ ] Update sync script
- [ ] Adjust merge strategy
- [ ] Other: ___________

## Additional Context
<!-- Add any logs, screenshots, or other context that might help. -->

---
*This issue was created automatically by the Upstream Sync Bot or manually for sync tracking.*
50 changes: 50 additions & 0 deletions .github/ISSUE_TEMPLATE/upstream_sync.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
name: Upstream Sync
description: Request sync from upstream repositories
title: "[UPSTREAM] Sync from "
labels: ["upstream"]
body:
- type: markdown
attributes:
value: |
Request a sync from upstream repositories.

- type: dropdown
id: source
attributes:
label: Upstream Source
description: Which upstream repository?
options:
- gemini-cli-extensions/conductor
- jnorthrup/conductor2
- Both
validations:
required: true

- type: textarea
id: changes
attributes:
label: Changes to Include
description: What specific changes should be synced?
placeholder: |
- PR #123
- Issue #456 fix
- New feature X
validations:
required: true

- type: textarea
id: rationale
attributes:
label: Rationale
description: Why do these changes need to be synced?
validations:
required: true

- type: checkboxes
id: checklist
attributes:
label: Checklist
options:
- label: I've reviewed the upstream changes
- label: These changes don't conflict with existing work
- label: I'm willing to help test the sync
Loading