codee-agent 0.5.0__tar.gz → 0.5.1__tar.gz

{codee_agent-0.5.0 → codee_agent-0.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codee-agent
-Version: 0.5.0
+Version: 0.5.1
 Summary: A virtual co-worker that picks up Jira and Azure DevOps tasks and solves them with coding agents.
 Keywords: ai,agent,jira,azure-devops,claude-code,github-copilot,automation
 Author: Denis Kibalko
@@ -35,11 +35,11 @@ Description-Content-Type: text/markdown
 
 # Codee - a virtual co-worker
 
-The goal of this project is to provide an assistant that will integrate into your existing environment in order to help you to solve tasks.
+The goal of this project is to provide an assistant that will integrate into your existing environment in order to help you to work on tasks (development, code review, testing).
 
-Codee works with Jira and Azure DevOps as tasks provider, new providers are quite easy to create, PRs are welcome.
+Codee works with Jira and Azure DevOps as tasks providers, new providers are quite easy to create, PRs are welcome.
 
-As agents it current works with Claude Code and Github Copilot.
+As agents it currently works with Claude Code and Github Copilot.
 
 ## Run Codee
 
@@ -71,6 +71,3 @@ uv run codee-start --debug-all   # ...plus reflex, boto3, urllib3 and friends
 ### Skills
 
 Codee uses skills to perform tasks. It is the same skills which are used in Claude Code, Codex and other agents.
-
-
-TODO: add skill types, x-codee skills extension

{codee_agent-0.5.0 → codee_agent-0.5.1}/README.md

@@ -1,10 +1,10 @@
 # Codee - a virtual co-worker
 
-The goal of this project is to provide an assistant that will integrate into your existing environment in order to help you to solve tasks.
+The goal of this project is to provide an assistant that will integrate into your existing environment in order to help you to work on tasks (development, code review, testing).
 
-Codee works with Jira and Azure DevOps as tasks provider, new providers are quite easy to create, PRs are welcome.
+Codee works with Jira and Azure DevOps as tasks providers, new providers are quite easy to create, PRs are welcome.
 
-As agents it current works with Claude Code and Github Copilot.
+As agents it currently works with Claude Code and Github Copilot.
 
 ## Run Codee
 
@@ -36,6 +36,3 @@ uv run codee-start --debug-all   # ...plus reflex, boto3, urllib3 and friends
 ### Skills
 
 Codee uses skills to perform tasks. It is the same skills which are used in Claude Code, Codex and other agents.
-
-
-TODO: add skill types, x-codee skills extension

{codee_agent-0.5.0 → codee_agent-0.5.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codee-agent"
-version = "0.5.0"
+version = "0.5.1"
 description = "A virtual co-worker that picks up Jira and Azure DevOps tasks and solves them with coding agents."
 readme = "README.md"
 license = "MIT"

{codee_agent-0.5.0 → codee_agent-0.5.1}/src/codee/admin_service.py

@@ -380,6 +380,15 @@ def _remove_redundant_skill_transitions(
         for transition in transitions:
             if transition is candidate or transition["label"].casefold() != label:
                 continue
+            # Another entry for the same pair is a duplicate, not a detour.
+            # Counting it would make each copy the "longer path" that deletes
+            # the other, and the edge would vanish entirely. A skill that
+            # states one transition in several places (story-planner names
+            # `AI Decomposition review` for both a finished plan and an open
+            # question) is exactly what makes the agent emit those copies.
+            if (transition["source"].casefold() == source
+                    and transition["target"].casefold() == target):
+                continue
             adjacency.setdefault(transition["source"].casefold(), set()).add(
                 transition["target"].casefold()
             )

{codee_agent-0.5.0 → codee_agent-0.5.1}/src/codee/templates/skills/story-code-reviewer/SKILL.md

@@ -3,7 +3,7 @@ name: story-code-reviewer
 description: Review a pull request for one subtask in an Issue Tracker story.
 disable-model-invocation: true
 x-codee-trigger: issue
-x-codee-issue-status: ['AI CR Needed']
+x-codee-issue-status: ['AI Ready for CR']
 x-codee-issue-type: story
 argument-hint: <STORY_ID>
 ---
@@ -19,6 +19,13 @@ argument-hint: <STORY_ID>
 5. Review security, correctness, requirement coverage, performance, tests, error handling, and maintainability.
 6. Post line comments for specific defects and a findings-first pull request review.
 7. Add a concise Issue Tracker comment with the verdict, blocking findings, and verification performed.
+8. Move the story to `AI Ready for security review` when the review passes, or back to `AI Ready for development` when it does not.
+
+## Status Transitions
+
+- Review passed with no blocking findings: move the story to `AI Ready for security review`.
+- Blocking findings, or a relevant failing pipeline: move the story to `AI Ready for development` so the developer skill addresses them.
+- Subtasks still awaiting review: leave the story in `AI Ready for CR` so the next run reviews the next one.
 
 ## Guidelines
 
@@ -26,4 +33,4 @@ argument-hint: <STORY_ID>
 - Distinguish blocking defects from optional suggestions.
 - Do not approve changes with unresolved blocking findings.
 - Do not approve a failing pipeline unless the failure is clearly unrelated.
-- Make feedback actionable by naming the observed behavior, expected behavior, and affected location.
+- Make feedback actionable by naming the observed behavior, expected behavior, and affected location.

codee_agent-0.5.1/src/codee/templates/skills/story-developer/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: story-developer
+description: Implement one subtask from an Issue Tracker story and submit a pull request.
+disable-model-invocation: true
+x-codee-trigger: issue
+x-codee-issue-status: ['AI Ready for development', 'AI In Progress']
+x-codee-issue-type: story
+argument-hint: <STORY_ID>
+---
+
+# Story Developer
+
+## Workflow
+
+1. Read the story, acceptance criteria, attachments, comments, and subtasks in the Issue Tracker.
+2. Read `story-spec/{STORY_ID}/README.md` and the affected projects' `CLAUDE.md`, `AGENTS.md`, and relevant local skills.
+3. Move the story to `AI In Progress` before doing any work, so a story already being worked on is not picked up as new.
+4. Select one open subtask and inspect any related branches, pull requests, and review comments.
+5. For bugs and regressions, reproduce the problem and identify the root cause before editing code.
+6. Create or reuse a dedicated worktree and branch according to repository conventions.
+7. Install dependencies, implement the smallest complete change, and update the story specification when useful.
+8. Run focused tests, the project build, and any required browser checks.
+9. Review the complete diff for correctness, security, regressions, and missing tests.
+10. Commit, push, and create or update the pull request. Do not merge it unless explicitly requested.
+11. Add a concise Issue Tracker comment describing the change, validation, pull request, and any remaining risk.
+12. Move the story to `AI Ready for CR` once every open subtask is implemented and its pull request is open.
+
+## Status Transitions
+
+- Work started: move the story to `AI In Progress`.
+- All subtasks implemented and pushed: move the story to `AI Ready for CR`.
+- Open subtasks remain: leave the story in `AI In Progress` so the next run continues the work.
+
+For UI work, include screenshots or video evidence when appropriate.

{codee_agent-0.5.0 → codee_agent-0.5.1}/src/codee/templates/skills/story-planner/SKILL.md

@@ -3,7 +3,7 @@ name: story-planner
 description: Decompose an Issue Tracker story into actionable subtasks and supporting documentation.
 disable-model-invocation: true
 x-codee-trigger: issue
-x-codee-issue-status: ['AI Decomposition Needed']
+x-codee-issue-status: ['AI Decomposition needed']
 x-codee-issue-type: story
 argument-hint: <STORY_ID>
 ---
@@ -29,8 +29,15 @@ Decompose an Issue Tracker story into actionable subtasks with supporting docume
 
 When a plan already exists, re-read new comments and edit the existing subtasks and specification. Create new subtasks only for newly identified work, and avoid duplicates. Move the story back to `AI Decomposition review` when the round is done.
 
+## Status Transitions
+
+- Plan posted: move the story to `AI Decomposition review`.
+- Waiting on answers to clarifying questions: move the story to `AI Decomposition review` and stop.
+
+Never move the story to `AI Ready for development` yourself. Approving the plan is a human decision.
+
 ## Guidelines
 
 - Prefer subtasks that can be implemented and reviewed independently.
 - Order subtasks by dependency.
-- Keep technical details concrete and acceptance criteria verifiable.
+- Keep technical details concrete and acceptance criteria verifiable.

{codee_agent-0.5.0 → codee_agent-0.5.1}/src/codee/templates/skills/story-qa/SKILL.md

@@ -24,5 +24,12 @@ Validate one subtask per invocation. QA is read-only: do not modify the implemen
 8. Mark each criterion pass or fail and separate blocking defects from non-blocking observations.
 9. Post a concise Issue Tracker report with the results, evidence, environment, and actionable reproduction steps for failures.
 10. Update the story specification with a short QA summary when useful.
+11. Move the story to `AI Ready for Human review` when every criterion passes, or back to `AI Ready for development` when any blocking defect was found.
 
-Create a separate Issue Tracker item for unrelated defects instead of expanding the subtask.
+## Status Transitions
+
+- Every applicable acceptance criterion passed: move the story to `AI Ready for Human review`.
+- Any blocking defect: move the story to `AI Ready for development` with the reproduction steps.
+- Subtasks still awaiting verification: leave the story in `AI Ready for QA` so the next run validates the next one.
+
+Create a separate Issue Tracker item for unrelated defects instead of expanding the subtask.

codee_agent-0.5.1/src/codee/templates/skills/story-security-reviewer/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: story-security-reviewer
+description: Run a security review of the pull request for one subtask in an Issue Tracker story.
+disable-model-invocation: true
+x-codee-trigger: issue
+x-codee-issue-status: ['AI Ready for security review']
+x-codee-issue-type: story
+argument-hint: <STORY_ID>
+---
+
+# Story Security Reviewer
+
+A security-only pass over work that already passed code review. In a general review, security findings compete with naming, tests, and performance and usually lose. This run looks at nothing else.
+
+## Workflow
+
+1. Read the story, acceptance criteria, attachments, comments, and linked subtasks in the Issue Tracker.
+2. Read `story-spec/{STORY_ID}/README.md` when it exists.
+3. Select one subtask whose pull request has passed code review.
+4. Read the project instructions, complete diff, affected files, and the trust boundaries the change touches.
+5. Review authentication, authorization, input validation, injection, secrets and credential handling, sensitive data exposure, unsafe deserialization, path and command handling, dependency risk, and access to third-party services.
+6. For each finding, record the vulnerable location, the attack it enables, and the concrete fix.
+7. Post line comments for specific vulnerabilities and a findings-first pull request review.
+8. Add a concise Issue Tracker comment with the verdict, blocking findings, and what was inspected.
+9. Move the story to `AI Ready for QA` when the review passes, or back to `AI Ready for development` when it does not.
+
+## Status Transitions
+
+- No exploitable findings: move the story to `AI Ready for QA`.
+- Any exploitable finding: move the story to `AI Ready for development` with the location and the fix.
+- Subtasks still awaiting a security pass: leave the story in `AI Ready for security review` so the next run reviews the next one.
+
+## Guidelines
+
+- Review one subtask per invocation.
+- Report only findings reachable in this codebase, and name the path that reaches them.
+- Separate exploitable vulnerabilities from hardening suggestions.
+- Do not modify the implementation or merge the pull request.

codee_agent-0.5.1/src/codee/templates/skills/task-code-reviewer/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: task-code-reviewer
+description: Review the pull request for a standalone Issue Tracker task.
+disable-model-invocation: true
+x-codee-trigger: issue
+x-codee-issue-status: ['AI Ready for CR']
+x-codee-issue-type: task
+argument-hint: <TASK_ID>
+---
+
+# Task Code Reviewer
+
+## Workflow
+
+1. Read the task, acceptance criteria, attachments, and comments in the Issue Tracker.
+2. Locate the pull request awaiting review.
+3. Read the project instructions, complete diff, affected files, relevant callers, tests, pipeline results, and unresolved review comments.
+4. Review security, correctness, requirement coverage, performance, tests, error handling, and maintainability.
+5. Post line comments for specific defects and a findings-first pull request review.
+6. Add a concise Issue Tracker comment with the verdict, blocking findings, and verification performed.
+7. Move the task to `AI Ready for security review` when the review passes, or back to `AI Ready for development` when it does not.
+
+## Status Transitions
+
+- Review passed with no blocking findings: move the task to `AI Ready for security review`.
+- Blocking findings, or a relevant failing pipeline: move the task to `AI Ready for development` so the developer skill addresses them.
+
+## Guidelines
+
+- Distinguish blocking defects from optional suggestions.
+- Do not approve changes with unresolved blocking findings.
+- Do not approve a failing pipeline unless the failure is clearly unrelated.
+- Make feedback actionable by naming the observed behavior, expected behavior, and affected location.

codee_agent-0.5.1/src/codee/templates/skills/task-developer/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: task-developer
+description: Implement a standalone Issue Tracker task and submit a pull request.
+disable-model-invocation: true
+x-codee-trigger: issue
+x-codee-issue-status: ['AI Ready for development', 'AI In Progress']
+x-codee-issue-type: task
+argument-hint: <TASK_ID> [continue]
+---
+
+# Task Developer
+
+## Workflow
+
+1. Read the task, acceptance criteria, attachments, and comments in the Issue Tracker. With `continue`, also read new pull request feedback.
+2. Read the affected projects' `CLAUDE.md`, `AGENTS.md`, and relevant local skills.
+3. Move the task to `AI In Progress` before doing any work, so a task already being worked on is not picked up as new.
+4. For bugs and regressions, reproduce the problem and identify the root cause before editing code. Report evidence when the issue cannot be reproduced or the root cause remains unclear.
+5. Create or reuse a dedicated worktree and branch according to repository conventions.
+6. Install dependencies and implement the smallest complete change that satisfies the acceptance criteria.
+7. Run focused tests, the project build, and browser validation for UI work.
+8. Review the complete diff for correctness, security, regressions, and missing tests.
+9. Commit, push, and create or update the pull request. Do not merge it unless explicitly requested.
+10. Add a concise Issue Tracker comment describing the change, validation, pull request, and any remaining risk.
+11. Move the task to `AI Ready for CR` once the change is complete and its pull request is open.
+
+## Status Transitions
+
+- Work started: move the task to `AI In Progress`.
+- Change complete and pushed: move the task to `AI Ready for CR`.
+- Work unfinished, or the problem could not be reproduced: leave the task in `AI In Progress` and comment with what is missing.
+
+For UI work, include screenshots or video evidence when appropriate. On continued work, always refresh the Issue Tracker item and pull request before acting.

{codee_agent-0.5.0 → codee_agent-0.5.1}/src/codee/templates/skills/task-qa/SKILL.md

@@ -22,5 +22,11 @@ QA is read-only: do not modify the implementation or merge its pull request.
 6. For service work, test success, validation, authorization, and edge cases. Record requests, responses, HTTP codes, and relevant side effects.
 7. Mark each criterion pass or fail and separate blocking defects from non-blocking observations.
 8. Post a concise Issue Tracker report with the results, evidence, environment, and actionable reproduction steps for failures.
+9. Move the task to `AI Ready for Human review` when every criterion passes, or back to `AI Ready for development` when any blocking defect was found.
 
-Create a separate Issue Tracker item for unrelated defects instead of expanding the task.
+## Status Transitions
+
+- Every acceptance criterion passed: move the task to `AI Ready for Human review`.
+- Any blocking defect: move the task to `AI Ready for development` with the reproduction steps.
+
+Create a separate Issue Tracker item for unrelated defects instead of expanding the task.

codee_agent-0.5.1/src/codee/templates/skills/task-security-reviewer/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: task-security-reviewer
+description: Run a security review of the pull request for a standalone Issue Tracker task.
+disable-model-invocation: true
+x-codee-trigger: issue
+x-codee-issue-status: ['AI Ready for security review']
+x-codee-issue-type: task
+argument-hint: <TASK_ID>
+---
+
+# Task Security Reviewer
+
+A security-only pass over work that already passed code review. In a general review, security findings compete with naming, tests, and performance and usually lose. This run looks at nothing else.
+
+## Workflow
+
+1. Read the task, acceptance criteria, attachments, and comments in the Issue Tracker.
+2. Locate the pull request that has passed code review.
+3. Read the project instructions, complete diff, affected files, and the trust boundaries the change touches.
+4. Review authentication, authorization, input validation, injection, secrets and credential handling, sensitive data exposure, unsafe deserialization, path and command handling, dependency risk, and access to third-party services.
+5. For each finding, record the vulnerable location, the attack it enables, and the concrete fix.
+6. Post line comments for specific vulnerabilities and a findings-first pull request review.
+7. Add a concise Issue Tracker comment with the verdict, blocking findings, and what was inspected.
+8. Move the task to `AI Ready for QA` when the review passes, or back to `AI Ready for development` when it does not.
+
+## Status Transitions
+
+- No exploitable findings: move the task to `AI Ready for QA`.
+- Any exploitable finding: move the task to `AI Ready for development` with the location and the fix.
+
+## Guidelines
+
+- Report only findings reachable in this codebase, and name the path that reaches them.
+- Separate exploitable vulnerabilities from hardening suggestions.
+- Do not modify the implementation or merge the pull request.

{codee_agent-0.5.0 → codee_agent-0.5.1}/src/codee/test_admin_service.py

@@ -13,8 +13,8 @@ from codee_agent_claude_code.provider import ClaudeCodeAgent
 from codee_agent_github_copilot.provider import GitHubCopilotAgent
 
 from codee.admin_service import (
-    MCP_CHECK, TASKS_CHECK, AdminService, azure_oauth, normalize_work_items,
-    parse_skill, repository_name)
+    MCP_CHECK, TASKS_CHECK, AdminService, _remove_redundant_skill_transitions,
+    azure_oauth, normalize_work_items, parse_skill, repository_name)
 from codee_main_context.context import (
     CodeeMainContext, CodingAgent, Settings, TasksProvider, load_settings,
     save_settings)
@@ -1676,5 +1676,70 @@ class SetupTasksMcpTest(unittest.TestCase):
             self.assertIn("not valid JSON", message)
 
 
+class RemoveRedundantSkillTransitionsTest(unittest.TestCase):
+    """Only a genuine detour removes an edge, never a repeated statement."""
+
+    def _transition(self, source: str, target: str, label: str,
+                    evidence: str) -> dict[str, str]:
+        return {"source": source, "target": target,
+                "label": label, "evidence": evidence}
+
+    def test_a_bypass_of_a_two_step_path_is_removed(self) -> None:
+        transitions = [
+            self._transition("Ready", "In progress", "dev", "first"),
+            self._transition("In progress", "Review", "dev", "second"),
+            self._transition("Ready", "Review", "dev", "third"),
+        ]
+
+        retained = _remove_redundant_skill_transitions(transitions)
+
+        self.assertEqual([(row["source"], row["target"]) for row in retained],
+                         [("Ready", "In progress"), ("In progress", "Review")])
+
+    def test_repeating_one_transition_keeps_it(self) -> None:
+        """A skill that names the same target twice still gets its edge.
+
+        story-planner moves the story to `AI Decomposition review` both when
+        the plan is ready and when it stops to ask a question, so the agent
+        reports the pair twice. Reading the second copy as a longer path made
+        each delete the other and the transition disappeared from the graph.
+        """
+        transitions = [
+            self._transition("AI Decomposition needed", "AI Decomposition review",
+                             "story-planner", "plan posted"),
+            self._transition("AI Decomposition needed", "AI Decomposition review",
+                             "story-planner", "questions asked"),
+        ]
+
+        retained = _remove_redundant_skill_transitions(transitions)
+
+        self.assertEqual(retained, transitions)
+
+    def test_a_duplicated_bypass_is_still_removed(self) -> None:
+        transitions = [
+            self._transition("Ready", "In progress", "dev", "first"),
+            self._transition("In progress", "Review", "dev", "second"),
+            self._transition("Ready", "Review", "dev", "third"),
+            self._transition("Ready", "Review", "dev", "fourth"),
+        ]
+
+        retained = _remove_redundant_skill_transitions(transitions)
+
+        self.assertEqual([(row["source"], row["target"]) for row in retained],
+                         [("Ready", "In progress"), ("In progress", "Review")])
+
+    def test_another_skill_bypass_is_left_alone(self) -> None:
+        """The detour has to belong to the same skill to count as one."""
+        transitions = [
+            self._transition("Ready", "In progress", "dev", "first"),
+            self._transition("In progress", "Review", "dev", "second"),
+            self._transition("Ready", "Review", "qa", "third"),
+        ]
+
+        retained = _remove_redundant_skill_transitions(transitions)
+
+        self.assertEqual(len(retained), 3)
+
+
 if __name__ == "__main__":
     unittest.main()

codee_agent-0.5.0/src/codee/templates/skills/story-developer/SKILL.md

@@ -1,26 +0,0 @@
----
-name: story-developer
-description: Implement one subtask from an Issue Tracker story and submit a pull request.
-disable-model-invocation: true
-x-codee-trigger: issue
-x-codee-issue-status: ['AI Ready for development', 'AI In Progress']
-x-codee-issue-type: story
-argument-hint: <STORY_ID>
----
-
-# Story Developer
-
-## Workflow
-
-1. Read the story, acceptance criteria, attachments, comments, and subtasks in the Issue Tracker.
-2. Read `story-spec/{STORY_ID}/README.md` and the affected projects' `CLAUDE.md`, `AGENTS.md`, and relevant local skills.
-3. Select one open subtask and inspect any related branches, pull requests, and review comments.
-4. For bugs and regressions, reproduce the problem and identify the root cause before editing code.
-5. Create or reuse a dedicated worktree and branch according to repository conventions.
-6. Install dependencies, implement the smallest complete change, and update the story specification when useful.
-7. Run focused tests, the project build, and any required browser checks.
-8. Review the complete diff for correctness, security, regressions, and missing tests.
-9. Commit, push, and create or update the pull request. Do not merge it unless explicitly requested.
-10. Add a concise Issue Tracker comment describing the change, validation, pull request, and any remaining risk.
-
-For UI work, include screenshots or video evidence when appropriate.

codee_agent-0.5.0/src/codee/templates/skills/task-developer/SKILL.md

@@ -1,25 +0,0 @@
----
-name: task-developer
-description: Implement a standalone Issue Tracker task and submit a pull request.
-disable-model-invocation: true
-x-codee-trigger: issue
-x-codee-issue-status: ['AI Ready for development', 'AI In Progress', Reopened]
-x-codee-issue-type: task
-argument-hint: <TASK_ID> [continue]
----
-
-# Task Developer
-
-## Workflow
-
-1. Read the task, acceptance criteria, attachments, and comments in the Issue Tracker. With `continue`, also read new pull request feedback.
-2. Read the affected projects' `CLAUDE.md`, `AGENTS.md`, and relevant local skills.
-3. For bugs and regressions, reproduce the problem and identify the root cause before editing code. Report evidence when the issue cannot be reproduced or the root cause remains unclear.
-4. Create or reuse a dedicated worktree and branch according to repository conventions.
-5. Install dependencies and implement the smallest complete change that satisfies the acceptance criteria.
-6. Run focused tests, the project build, and browser validation for UI work.
-7. Review the complete diff for correctness, security, regressions, and missing tests.
-8. Commit, push, and create or update the pull request. Do not merge it unless explicitly requested.
-9. Add a concise Issue Tracker comment describing the change, validation, pull request, and any remaining risk.
-
-For UI work, include screenshots or video evidence when appropriate. On continued work, always refresh the Issue Tracker item and pull request before acting.