[AI Docs] Reorganize documentation into structured folder #12
@@ -518,3 +518,30 @@ When requesting implementations:
|
|||||||
- Constraints (Resource usage, signal conventions)
|
- Constraints (Resource usage, signal conventions)
|
||||||
|
|
||||||
**When in doubt:** Reference `AI_HELP.md` for project-specific conventions before asking questions.
|
**When in doubt:** Reference `AI_HELP.md` for project-specific conventions before asking questions.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Note About `make-pr` Skill Availability
|
||||||
|
|
||||||
|
The **`make-pr`** skill (`.opencode/skills/make-pr.json`) is available for use! This skill will:
|
||||||
|
- Generate comprehensive, human-readable PR descriptions
|
||||||
|
- List testing strategies for each change area
|
||||||
|
- Validate changes before PR creation
|
||||||
|
- Format PR descriptions with clear sections
|
||||||
|
|
||||||
|
**When to use `make-pr` skill:**
|
||||||
|
- When ready to submit a PR from your current branch (any platform)
|
||||||
|
- Before pushing code that requires peer review
|
||||||
|
- To ensure all changes are properly documented and validated
|
||||||
|
- When creating PRs for features, fixes, or refactoring
|
||||||
|
|
||||||
|
The skill automatically adapts to your hosting platform:
|
||||||
|
- **GitHub:** Creates PR via API with comprehensive descriptions
|
||||||
|
- **Gitea:** Falls back to web UI creation (URL provided above)
|
||||||
|
|
||||||
|
**Prompt example:**
|
||||||
|
```
|
||||||
|
"Create a pull request from move_docs to develop. The changes include moving
|
||||||
|
all AI documentation files into an 'AI Docs' folder with organized structure."
|
||||||
|
```
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user