44 lines
1.3 KiB
Markdown
44 lines
1.3 KiB
Markdown
<!--# cspell: ignore SSOT CMDB -->
|
|
# AGENTS.md
|
|
|
|
Ensure that all practices and instructions described by
|
|
https://raw.githubusercontent.com/ansible/ansible-creator/refs/heads/main/docs/agents.md
|
|
are followed.
|
|
|
|
## Repository Actions
|
|
|
|
**Use gitea-mcp tools for all repository interactions.** Do not use `curl`, `git`, or direct API calls.
|
|
|
|
### When to Use gitea-mcp
|
|
|
|
- Fetching issues, PRs, branches, tags, releases
|
|
- Reading files, directories, or commits from repo
|
|
- Creating issues, PRs, comments, tags, or releases
|
|
- Editing issues or PRs
|
|
|
|
### Wrong vs Right
|
|
|
|
❌ `curl http://git.valid.dk/api/v1/repos/daniel/ansible-bind9-role/issues/6`
|
|
|
|
✅ `mcp_gitea-mcp_list_repo_issues(owner, repo, page, pageSize)`
|
|
|
|
### Local Workspace
|
|
|
|
Terminal commands are fine for:
|
|
- Compiling, testing, building
|
|
- Git operations on local files (commit, push)
|
|
- Using `read_file`, `grep_search`, `semantic_search`
|
|
|
|
## General project workflow
|
|
1. Check for open tickets
|
|
2. Choose next logical ticket to work on
|
|
3. Create branch for ticket
|
|
4. Create plan for ticket
|
|
5. Execute plan
|
|
6. Create appropriate commits to repository
|
|
7. Submit PR to repository
|
|
8. Review the PR critically
|
|
9. Check if further work is needed to resolve the issues found
|
|
10. Loop 8-9 until complete
|
|
11. Ask me to review the PR and merge it
|
|
12. Close the ticket |