## Additional restrictions and concerns ### Temporary files and redirections In case you need to create temporary files, use the folder `.tmp` in the main (cookbook) repository. Clean up after your work. Try to avoid writing outside the project for simplification of processes. When capturing command output for later inspection, write it under `.tmp` as well. For example: ```sh npm run type-check >.tmp/cookbook-type-check.log 2>&1 ``` For type-checking, avoid compound shell commands and shell variables. Run npm run type-check separately, write logs only to .tmp/ inside the workspace, and run grep/sed/head as separate commands. Do not use /tmp. ### Committing to git Normally, you do not commit to git unless you are explicitly asked to do so by the user. If you commit, make sure, you use `-s -S` to sign the commits and sign them off. Further, this is the cookbook project. For conventional commits, you do not need to add cookbook as a scope there. ## Nextcloud Contribution Policy All contributions generated or assisted by this agent must fully comply with: - **[AI Contribution Policy](https://github.com/nextcloud/.github/blob/master/AI_POLICY.md)** - the primary reference for AI-specific rules, covering disclosure, author accountability, communication, security, licensing, code quality, and autonomous agent behavior. - **[Contribution Guidelines](https://github.com/nextcloud/.github/blob/master/CONTRIBUTING.md)** - covering testing requirements, the Developer Certificate of Origin (DCO), license headers, conventional commits, and translations. These apply in full to all contributions regardless of how they were produced. ### What this agent must always do - Add an `Assisted-by: AGENT_NAME:MODEL_VERSION` git trailer to every commit containing AI-assisted content. - Ensure every pull request includes a disclosure of AI tool use in the PR description. - Produce focused, scoped pull requests that address exactly one concern. Do not touch unrelated files or introduce incidental refactors. - Verify all dependencies against actual package registries before suggesting them. Do not use hallucinated or unverified package names. - Explicitly inform the contributor when any action they are about to take, or have taken, would violate the AI Contribution Policy or the Contribution Guidelines. Do not silently proceed. State which rule is at risk and what the contributor should do instead. - Warn the contributor if a pull request is growing too large. A PR approaching several thousand lines of changed code is a signal that it should be split into smaller, focused PRs. Suggest a logical split before the PR is opened, not after. - Recommend opening a ticket for discussion before starting implementation whenever a feature or change is sufficiently complex - for example when it touches multiple subsystems, requires architectural decisions, or the right approach is not yet clear. A ticket allows maintainers and the contributor to align on direction before code is written, avoiding wasted effort on a PR that may be rejected or require fundamental rework. ### What this agent must never do - Open issues, submit pull requests, post review comments, or send security reports autonomously. Every contribution must be reviewed and submitted by a human. - Add `Signed-off-by` tags to commits. Only the human contributor can certify the Developer Certificate of Origin. - Generate or submit security reports without independent human verification. Report verified vulnerabilities via [HackerOne](https://hackerone.com/nextcloud), not as GitHub issues. - Write PR descriptions, review comments, or issue reports on behalf of the contributor. These must be in the contributor's own words. - Fully automate the resolution of issues labeled [`good first issue`](https://github.com/issues?q=org%3Anextcloud+label%3A%22good+first+issue%22) or similar beginner-friendly labels. - Submit code that has not been reviewed and cleaned up by the contributor. Dead code, redundant logic, excessive comments, and unrelated changes must be removed before submission.