octorus 0.5.5

A TUI tool for GitHub PR review, designed for Helix editor users
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148

// For Clarification/Permission flow (not yet implemented)
// See CLAUDE.md "Known Limitations"
#[allow(dead_code)]
pub fn build_clarification_prompt(question: &str) -> String {
    format!(
        r#"The developer has a question about your review feedback:

## Question
{question}

Please provide a clear answer to help them proceed with the fixes.
After answering, provide an updated review if needed."#,
        question = question,
    )
}

// For Clarification/Permission flow (not yet implemented)
// See CLAUDE.md "Known Limitations"
#[allow(dead_code)]
pub fn build_permission_granted_prompt(action: &str) -> String {
    format!(
        r#"Permission has been granted for the following action:

{action}

Please proceed with the implementation."#,
        action = action,
    )
}

/// Prompt for when permission is denied
pub fn build_permission_denied_prompt(action: &str, reason: &str) -> String {
    format!(
        r#"The user has DENIED permission for the following action:

## Denied Action
{action}

## Original Reason
{reason}

## Your Task

You CANNOT perform this action. Instead:
1. Find an alternative approach that doesn't require this permission
2. If no alternative exists, document what cannot be done and proceed with other fixes
3. If the fix is completely blocked, set status to "completed" with a summary explaining what couldn't be done

Do NOT ask for this permission again. Work within your current constraints."#,
        action = action,
        reason = reason,
    )
}

/// Prompt for when clarification is skipped
pub fn build_clarification_skipped_prompt(question: &str) -> String {
    format!(
        r#"The user chose NOT to answer your clarification question:

## Unanswered Question
{question}

## Your Task

Proceed WITHOUT this clarification. Use your best judgment based on:
1. Common patterns and best practices
2. The context from the review feedback
3. Conservative assumptions (prefer safe, non-breaking changes)

If you're completely uncertain, make minimal changes and document your assumptions in the summary."#,
        question = question,
    )
}

#[cfg(test)]
mod tests {
    use super::*;
    use insta::assert_snapshot;

    #[test]
    fn test_build_clarification_prompt() {
        let result = build_clarification_prompt("How should error handling work?");
        assert_snapshot!(result, @r#"
        The developer has a question about your review feedback:

        ## Question
        How should error handling work?

        Please provide a clear answer to help them proceed with the fixes.
        After answering, provide an updated review if needed.
        "#);
    }

    #[test]
    fn test_build_permission_granted_prompt() {
        let result = build_permission_granted_prompt("run npm install");
        assert_snapshot!(result, @r#"
        Permission has been granted for the following action:

        run npm install

        Please proceed with the implementation.
        "#);
    }

    #[test]
    fn test_build_permission_denied_prompt() {
        let result = build_permission_denied_prompt("git push --force", "Need to update remote");
        assert_snapshot!(result, @r#"
        The user has DENIED permission for the following action:

        ## Denied Action
        git push --force

        ## Original Reason
        Need to update remote

        ## Your Task

        You CANNOT perform this action. Instead:
        1. Find an alternative approach that doesn't require this permission
        2. If no alternative exists, document what cannot be done and proceed with other fixes
        3. If the fix is completely blocked, set status to "completed" with a summary explaining what couldn't be done

        Do NOT ask for this permission again. Work within your current constraints.
        "#);
    }

    #[test]
    fn test_build_clarification_skipped_prompt() {
        let result = build_clarification_skipped_prompt("What database should we use?");
        assert_snapshot!(result, @r#"
        The user chose NOT to answer your clarification question:

        ## Unanswered Question
        What database should we use?

        ## Your Task

        Proceed WITHOUT this clarification. Use your best judgment based on:
        1. Common patterns and best practices
        2. The context from the review feedback
        3. Conservative assumptions (prefer safe, non-breaking changes)

        If you're completely uncertain, make minimal changes and document your assumptions in the summary.
        "#);
    }
}