Skip to content

Conversation

@pmaojo
Copy link

@pmaojo pmaojo commented Nov 29, 2025

PR Guideline

Typically, PRs should consist of a single commit, and so should generally follow
the rules for Go commit messages.

You must follow the form:

net/http: handle foo when bar

[longer description here in the body]

Fixes #12345

Notably, for the subject (the first line of description):

  • the name of the package affected by the change goes before the colon
  • the part after the colon uses the verb tense + phrase that completes the blank in, “this change modifies this package to ___________”
  • the verb after the colon is lowercase
  • there is no trailing period
  • it should be kept as short as possible

Additionally:

  • Markdown is allowed.
  • For a pervasive change, use "all" in the title instead of a package name.
  • The PR description should provide context (why this change?) and describe the changes
    at a high level. Changes that are obvious from the diffs don't need to be mentioned.

Implement the Vibecoder Server, an MCP server for architectural validation and BDD traceability.
- Implements Hexagonal Architecture rule enforcement.
- Implements Golden Thread traceability (Requirements -> Code -> Tests).
- Uses tree-sitter for TypeScript and Java parsing.
- Includes custom Gherkin parser.
- Exposes MCP tools: scaffold_feature, link_requirement, blast_radius.
- Exposes MCP resources: status, violations, traceability_matrix.
Implement the Vibecoder Server, an MCP server for architectural validation and BDD traceability.
- Implements Hexagonal Architecture rule enforcement.
- Implements Golden Thread traceability (Requirements -> Code -> Tests).
- Uses tree-sitter for TypeScript and Java parsing.
- Includes custom Gherkin parser.
- Exposes MCP tools: scaffold_feature, link_requirement, blast_radius.
- Exposes MCP resources: status, violations, traceability_matrix, architecture_diagram (Excalidraw).
- Provides architecture diagram in Excalidraw JSON format.
@jba
Copy link
Contributor

jba commented Dec 3, 2025

Before writing a PR of this size, please file an issue explaining what you are doing and why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants