Buildforce is open source and welcomes contributions! We're building the future of AI-assisted development together.
git clone https://github.com/berserkdisruptors/buildforce-cli.git
cd buildforce-cli
npm install
npm run build
npm link
Now you can test your changes in any project:
cd ~/my-test-project
buildforce init .
Make changes, rebuild, and test:
# Make code changes
npm run build
npm link
# Test in another project
cd ~/my-test-project
buildforce init .
Browse open issues to find something to work on:
If you found a bug or have a feature idea:
**Bug Report Template:**
## Description
Clear description of the bug
## Steps to Reproduce
1. Run command X
2. Observe error Y
## Expected Behavior
What should happen
## Actual Behavior
What actually happens
## Environment
- OS: macOS / Linux / Windows
- Buildforce version: v0.0.29
- AI Assistant: Cursor / Claude Code / etc.
**Feature Request Template:**
## Feature Description
What feature would you like?
## Use Case
Why is this feature needed?
## Proposed Solution
How might this work?
## Alternatives Considered
Other approaches you've thought about
Create a feature branch:
git checkout -b feature/add-new-command
git checkout -b fix/pagination-bug
git checkout -b docs/improve-readme
Follow the structured workflow:
# Research the codebase
/research how slash commands are implemented
# Define your spec
/spec Add /iterate command for plan refinement
# Build the feature
/build
# Complete and document
/complete
Pro tip: Use Buildforce to build Buildforce! Your spec and context files will help other contributors understand your changes.
Test your changes thoroughly:
# Build
npm run build
# Link locally
npm link
# Test in a fresh project
cd ~/test-project
buildforce init .
# Test your changes
/research test query
/spec Test feature
/build
/complete
**PR Template:**
## Description
Brief description of what this PR does
## Related Issue
Closes #123
## Changes Made
- Added feature X
- Fixed bug Y
- Updated documentation Z
## Testing
- [ ] Tested locally with npm link
- [ ] All existing tests pass
- [ ] Added new tests for changes
- [ ] Documentation updated
## Checklist
- [ ] Code follows project style
- [ ] Commit messages are clear
- [ ] No breaking changes (or clearly documented)
Follow conventional commits:
# Features
git commit -m "feat: add /iterate command for plan refinement"
# Bug fixes
git commit -m "fix: resolve spec parsing error with YAML arrays"
# Documentation
git commit -m "docs: improve /research command examples"
# Refactoring
git commit -m "refactor: extract spec validation into separate module"
# Tests
git commit -m "test: add integration tests for /build command"
# Run all tests
npm test
# Run specific test file
npm test src/commands/research.test.ts
# Run with coverage
npm run test:coverage
Add tests for new features:
describe('/research command', () => {
it('should search context repository', async () => {
const result = await research('authentication patterns');
expect(result).toContain('authentication-module.yaml');
});
});
Update docs for any user-facing changes:
buildforce-cli/
├── src/
│ ├── commands/ # Command implementations
│ │ ├── research.ts
│ │ ├── spec.ts
│ │ ├── build.ts
│ │ ├── complete.ts
│ │ └── document.ts
│ ├── templates/ # YAML templates
│ ├── scripts/ # Build and utility scripts
│ └── utils/ # Shared utilities
├── tests/ # Test files
├── .starters/ # Command file templates
│ ├── claude/
│ ├── cursor/
│ └── ... (other AI assistants)
├── package.json
├── tsconfig.json
└── README.md
All contributors are recognized in:
By contributing, you agree that your contributions will be licensed under the Apache License 2.0.