AutoGPT is the vision of accessible AI for everyone, to use and to build on. Our mission is to provide the tools, so that you can focus on what matters.
dx(skills): codify PR workflow rules in skill docs and CLAUDE.md (#12531)
Zamil Majdy1771ed3befa9
diff --git a/.claude/skills/pr-address/SKILL.md b/.claude/skills/pr-address/SKILL.mdindex 8e6f63e45e..a0c4690454 100644--- a/.claude/skills/pr-address/SKILL.md+++ b/.claude/skills/pr-address/SKILL.md@@ -113,7 +113,9 @@ kill $REST_PID 2>/dev/null; trap - EXIT```Never manually edit files in `src/app/api/__generated__/`.-Then commit and **push immediately** — never batch commits without pushing.+Then commit and **push immediately** — never batch commits without pushing. Each fix should be visible on GitHub right away so CI can start and reviewers can see progress.++**Never push empty commits** (`git commit --allow-empty`) to re-trigger CI or bot checks. When a check fails, investigate the root cause (unchecked PR checklist, unaddressed review comments, code issues) and fix those directly. Empty commits add noise to git history.For backend commits in worktrees: `poetry run git commit` (pre-commit hooks).diff --git a/autogpt_platform/CLAUDE.md b/autogpt_platform/CLAUDE.mdindex d9fc626137..bd6c59f513 100644--- a/autogpt_platform/CLAUDE.md+++ b/autogpt_platform/CLAUDE.md@@ -53,6 +53,7 @@ AutoGPT Platform is a monorepo containing:### Creating Pull Requests- Create the PR against the `dev` branch of the repository.+- **Split PRs by concern** — each PR should have a single clear purpose. For example, "usage tracking" and "credit charging" should be separate PRs even if related. Combining multiple concerns makes it harder for reviewers to understand what belongs to what.- Ensure the branch name is descriptive (e.g., `feature/add-new-block`)- Use conventional commit messages (see below)- **Structure the PR description with Why / What / How** — Why: the motivation (what problem it solves, what's broken/missing without it); What: high-level summary of changes; How: approach, key implementation details, or architecture decisions. Reviewers need all three to judge whether the approach fits the problem.diff --git a/autogpt_platform/backend/CLAUDE.md b/autogpt_platform/backend/CLAUDE.mdindex 0da4de54bd..8ff251844c 100644--- a/autogpt_platform/backend/CLAUDE.md+++ b/autogpt_platform/backend/CLAUDE.md@@ -61,6 +61,7 @@ poetry run pytest path/to/test.py --snapshot-update## Code Style- **Top-level imports only** — no local/inner imports (lazy imports only for heavy optional deps like `openpyxl`)+- **Absolute imports** — use `from backend.module import ...` for cross-package imports. Single-dot relative (`from .sibling import ...`) is acceptable for sibling modules within the same package (e.g., blocks). Avoid double-dot relative imports (`from ..parent import ...`) — use the absolute path instead- **No duck typing** — no `hasattr`/`getattr`/`isinstance` for type dispatch; use typed interfaces/unions/protocols- **Pydantic models** over dataclass/namedtuple/dict for structured data- **No linter suppressors** — no `# type: ignore`, `# noqa`, `# pyright: ignore`; fix the type/code