How to review PRs with project-specific context

​

Ways to provide context

​

Memories

@fossy remember: this project uses hexagonal architecture.
Domain layer must never depend on infrastructure.

​

File references in rules

Instructions: Validate that new endpoints follow the patterns
in @file:docs/api-conventions.md and use the base classes
defined in @file:src/shared/base-controller.ts.

​

Custom prompts

1. Go to Code Review Settings → Custom Prompts
2. Add context like architecture descriptions, team guidelines, or domain knowledge
3. Fossy includes this in every code review analysis

​

MCP plugins

• Jira/Linear — task requirements and acceptance criteria
• Slack — team discussions and decisions
• Google Docs — specs and design documents
• Custom MCP servers — any tool your team uses

​

Example workflow

1. Define architecture rules via Memories: @fossy remember: we follow CQRS pattern in this service
2. Create Review Rules that reference your docs: @file:docs/architecture.md
3. Connect Jira so Fossy validates PRs against task requirements
4. Add Custom Prompts for domain-specific knowledge