Skip to content

Commit 794a659

Browse files
authored
Merge pull request #37 from project-codeguard/docs/faq-context-window
docs: Update CONTRIBUTING.md and FAQ
2 parents ffe81d2 + 943af6d commit 794a659

File tree

2 files changed

+20
-9
lines changed

2 files changed

+20
-9
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -116,15 +116,10 @@ Maintainers aim to review pull requests and issues within 3 business days.
116116
- `main` – main development branch and authoritative source; updated after community approval for content changes
117117
- `develop` – staging area for community review of content updates; feature branches for content changes target this branch
118118
- `feature` – feature/this-is-a-new-feature-branch (target `develop` for content updates, `main` for non-content changes)
119-
- `codebugfix` – codebugfix/name-of-the-bug (typically targets `main`)
120-
- `languagefix` – languagefix/fix-details (typically targets `main`)
121-
- `release` – release/1.0.0 – cut from `main` when ready
122-
123-
### Rebasing note
124-
125-
**For content updates**: After completing work on a feature branch, rebase on `develop` before opening a PR. After PR approval, rebase again to ensure the latest `develop` changes are included before merging.
126-
127-
**For non-content changes**: After completing work on a feature branch, rebase on `main` before opening a PR. After PR approval, rebase again to ensure the latest `main` changes are included before merging.
119+
- `codebugfix` – codebugfix/description-of-the-bug (typically targets `main`)
120+
- `languagefix` – languagefix/description-of-the-language-fix (typically targets `main`)
121+
- `docs` – docs/description-of-the-documentation-change (typically targets `main`; documentation changes are exempt from the content update rule above)
122+
- `release` – release/description-of-the-release – cut from `main` when ready
128123

129124
### Commit messages format
130125

docs/faq.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,22 @@ This FAQ document provides clear, concise answers to help developers seamlessly
2323
- **GitHub Copilot**: Copy `.github/instructions/` directory to your project root
2424
3. Restart your IDE and start coding - the AI assistant will automatically follow the security rules
2525

26+
---
27+
## Q: Will these rules consume a lot of the AI agent's **context window**?
28+
29+
**A:** No. The always-on rules are designed to be lightweight and efficient, and should not consume a lot of the AI agent's context window. The "glob" rules are designed to be applied only to the related file types specified in the rule.
30+
31+
---
32+
## Q: What is the `additional_rules` folder?
33+
34+
**A:** The `additional_rules` folder contains rules that can be used to supplement the Project CodeGuard core rules. These rules are not always-on and are not included in the downloaded release. They are only available in the `project-codeguard/rules` repository for code review and security assessments post-code generation.
35+
36+
---
37+
38+
## Q: How can I use the rules in my own AI agent?
39+
40+
**A:** You can use the rules in your own AI agent by creating a custom ruleset. You can create a custom ruleset by creating a new file in the `.cursor/rules`, `.windsurf/rules`, or `.github/instructions` directories and adding the rules you want to apply. You can also use the `project-codeguard/rules` repository as a template to create your own ruleset.
41+
2642
---
2743

2844
## Q: Why does the downloaded release folder appear empty?

0 commit comments

Comments
 (0)