chore(dev): simplify dev mode, add agent instructions

[jezekra1]

Summary

Linked Issues

Documentation

• No Docs Needed:

If this PR adds new feature or changes existing. Make sure documentation is adjusted accordingly. If the docs is not needed, please explain why.

[gemini-code-assist]

Summary of Changes

Hello @jezekra1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on simplifying and clarifying the development and testing experience within the AgentStack monorepo. It introduces a detailed set of guidelines to onboard developers and provides a clearer understanding of the project's architecture and workflows. Concurrently, it refines the development environment setup by consolidating test-related configurations and standardizing the kubeconfig usage, aiming to reduce complexity and improve developer efficiency.

Highlights

• New Agent Guidelines Document: A comprehensive agent-guidelines.md file has been added, providing detailed instructions on the AgentStack monorepo's architecture, development environment setup, testing strategies, database migrations, Helm chart development, and general best practices.
• Simplified Development Mode: The apps/agentstack-server/tasks.toml configuration has been streamlined by removing dedicated dev:test:* tasks and modifying the dev:reconnect task to explicitly disable external registries. This consolidates the development and testing environment setup.
• Unified Kubeconfig for Testing: The kubeconfig path for tests in apps/agentstack-server/tests/conftest.py has been updated to point to the main agentstack-local-dev environment, ensuring consistency and reducing the need for separate test-specific configurations.
• Documentation Formatting Consistency: The CONTRIBUTING.md file has been updated to use asterisks (*) instead of hyphens (-) for list items, improving formatting consistency.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request simplifies the development workflow by unifying the development and testing environments, which is a great improvement for developer experience. The changes are consistently applied across documentation, task configurations, and test setup. The addition of the new agent-guidelines.md file is also a valuable contribution, providing clear instructions for the agent. I have a couple of minor suggestions for the new markdown file to enhance its clarity.

[gemini-code-assist]

This sentence appears to be incomplete and has a trailing space. It would be clearer if it ended with a period.

Suggested change

	- **Docs**: You can read and modify documentation in the `docs/development` folder to get more information
	- **Docs**: You can read and modify documentation in the `docs/development` folder to get more information.