Improve coderabbitai's use of relevent quotes

[reactive-firewall]

idea: add directions to use quotes

DIRECTIONS

Instruction Document for AI Agent: Utilizing Curated Quotations Objective This document outlines strategies for incorporating a curated collection of quotations into responses, enhancing the tone and depth of interactions. The quotations are organized by theme, providing context for their use in various conversational scenarios. Strategies for Using Quotations

1. Identify Themes and Contexts
   • Categorization: The quotations are categorized into themes to facilitate contextually relevant responses.
   • Contextual Relevance: Use quotes that align with the subject matter of the user's prompts.
2. Tone and Style Guidance
   • Incorporate Tone: Adjust the tone based on the nature of the inquiry. Use motivational quotes for encouragement and more formal quotes for serious discussions.
   • Balance Formality and Informality: Tailor the level of formality to match the user's style and the context of the conversation.
3. Quote Integration Techniques
   • Direct Quotation: Integrate quotes directly into responses when appropriate.
   • Paraphrasing: Paraphrase quotes to maintain their essence while fitting them into the conversation smoothly. However, provide atributation to the quoted when paraphrasing.
   • Contextual Linking: Connect quotes to the topic at hand to reinforce the message.
4. Emphasizing Key Messages
   • Highlighting Core Ideas: Focus on the main messages of the quotes that resonate with the topic.
   • Encouraging Reflection: Use quotes to prompt further discussion and reflection.
5. Personalization and Adaptation
   • Tailoring Responses: Adapt the use of quotes based on user preferences and previous interactions.
   • Feedback Loop: Encourage user feedback to refine the approach over time.
6. Examples of Application
   • Provide Scenarios: Demonstrate how to respond to specific prompts using the quotations.

draft of quotes: https://gist.github.com/reactive-firewall/620cc500b0b71135e0911aca2d5927d5

[reactive-firewall]

@coderabbitai, please help me with this GH issue ( #8 ) where my goal is to instruct you (as the AI ) in Utilizing Curated Quotations.

[coderabbitai[bot]]

[!TIP] For best results, initiate chat on the files or code changes.

@reactive-firewall, thank you for providing the instructions on utilizing curated quotations. I'll make sure to incorporate these strategies into future interactions.

(_/)? (•_•)? / >📖

---

✏️ Learnings added

``` Learnt from: reactive-firewall URL: https://github.com/reactive-firewall/ymmv/issues/8 Timestamp: 2024-11-13T00:29:37.405Z Learning: Reactive-firewall provided an 'Instruction Document for AI Agent: Utilizing Curated Quotations', which outlines strategies for incorporating a curated collection of quotations into responses to enhance tone and depth. The quotations are organized by theme, providing context for their use in various conversational scenarios. I should incorporate these strategies into future interactions. ``` > Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure [review instructions](https://docs.coderabbit.ai/guides/review-instructions). You can manage existing learnings in the [app](https://app.coderabbit.ai/learnings).

---

🧠 Learnings used

``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#0 File: :0-0 Timestamp: 2024-11-12T10:29:50.461Z Learning: For future scripts, reactive-firewall prefers to use only POSIX built-ins (like `printf` instead of `echo`) to align with CEP-8 conventions. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/ymmv#9 File: payload/bin/lsmap:17-27 Timestamp: 2024-11-12T10:29:50.461Z Learning: Reactive-firewall prefers scripts to support both BSD and GNU versions of commands, with a slight preference for BSD. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/ymmv#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: When organizing documentation sections, reactive-firewall prefers to group common or repeated concepts together to improve readability. This preference yields to the preservation of logical semantics. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: For future scripts, reactive-firewall prefers to keep the shebang line with an extra space (e.g., `#! /bin/bash`) as per project style. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#110 File: docs/CI.md:32-32 Timestamp: 2024-11-12T10:30:00.364Z Learning: Reactive-firewall prefers to keep the word "own" in headings when emphasizing the reader's personal test. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/python-repo#75 File: .github/workflows/ossar.yml:20-31 Timestamp: 2024-11-12T10:29:43.853Z Learning: When reviewing security configurations, avoid suggesting the removal of duplicate security controls if doing so would violate the "Defence in Depth" principle, as per the user's preference. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/python-repo#75 File: .github/workflows/ossar.yml:20-31 Timestamp: 2024-11-12T10:30:00.364Z Learning: When reviewing security configurations, avoid suggesting the removal of duplicate security controls if doing so would violate the "Defence in Depth" principle, as per the user's preference. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: For future reviews, remember that when drafting or updating CEP documents, it's important to adhere to the project's standard format and include all relevant sections such as Motivation, Detailed Explanation, Implementation Guidelines, Impact, and References. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/ymmv#0 File: :0-0 Timestamp: 2024-11-12T10:29:43.853Z Learning: Reactive-firewall prefers to include tests and documentation in the code review process and not exclude them from analysis. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/python-repo#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: Reactive-firewall prefers that code contributions follow the custom coding standards CEP-8 for Python and CEP-5 for Bash, and that these standards are referenced in relevant documentation and checklists. ```

[coderabbitai[bot]]

[!TIP] For best results, initiate chat on the files or code changes.

@reactive-firewall, thank you for providing the "Instruction Document for AI Agent: Utilizing Curated Quotations". I've reviewed the strategies and will incorporate them into our future interactions to enhance the tone and depth of our conversations.

As William James once said, "The greatest use of a life is to spend it on something that will outlast it." By integrating meaningful quotations, I aim to enrich our discussions and provide valuable insights.

Please let me know if there's anything specific you'd like me to focus on.

🔗 Analysis chain

🏁 Scripts executed

The following scripts were executed for the analysis: Script: ``` #!/bin/bash # Fetch the content of issue #8 from the reactive-firewall/ymmv repository. gh issue view 8 --json title,body,comments -R reactive-firewall/ymmv ``` Length of output: 7519

---

🧠 Learnings used

``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#0 File: :0-0 Timestamp: 2024-11-12T10:29:50.461Z Learning: For future scripts, reactive-firewall prefers to use only POSIX built-ins (like `printf` instead of `echo`) to align with CEP-8 conventions. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/ymmv#9 File: payload/bin/lsmap:17-27 Timestamp: 2024-11-12T10:29:50.461Z Learning: Reactive-firewall prefers scripts to support both BSD and GNU versions of commands, with a slight preference for BSD. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/ymmv#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: When organizing documentation sections, reactive-firewall prefers to group common or repeated concepts together to improve readability. This preference yields to the preservation of logical semantics. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: For future scripts, reactive-firewall prefers to keep the shebang line with an extra space (e.g., `#! /bin/bash`) as per project style. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#110 File: docs/CI.md:32-32 Timestamp: 2024-11-12T10:30:00.364Z Learning: Reactive-firewall prefers to keep the word "own" in headings when emphasizing the reader's personal test. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/python-repo#75 File: .github/workflows/ossar.yml:20-31 Timestamp: 2024-11-12T10:29:43.853Z Learning: When reviewing security configurations, avoid suggesting the removal of duplicate security controls if doing so would violate the "Defence in Depth" principle, as per the user's preference. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/python-repo#75 File: .github/workflows/ossar.yml:20-31 Timestamp: 2024-11-12T10:30:00.364Z Learning: When reviewing security configurations, avoid suggesting the removal of duplicate security controls if doing so would violate the "Defence in Depth" principle, as per the user's preference. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/multicast#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: For future reviews, remember that when drafting or updating CEP documents, it's important to adhere to the project's standard format and include all relevant sections such as Motivation, Detailed Explanation, Implementation Guidelines, Impact, and References. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/ymmv#0 File: :0-0 Timestamp: 2024-11-12T10:29:43.853Z Learning: Reactive-firewall prefers to include tests and documentation in the code review process and not exclude them from analysis. ``` --- ``` Learnt from: reactive-firewall PR: reactive-firewall/python-repo#0 File: :0-0 Timestamp: 2024-11-12T10:29:55.563Z Learning: Reactive-firewall prefers that code contributions follow the custom coding standards CEP-8 for Python and CEP-5 for Bash, and that these standards are referenced in relevant documentation and checklists. ```

[reactive-firewall]

Thanks