agentic-devtools 0.0.10__tar.gz

agentic_devtools-0.0.10/.devcontainer/README.md

@@ -0,0 +1,53 @@
+# Python Development Container
+
+This directory contains the configuration for a Python development container that can be used with:
+
+- Visual Studio Code with the Dev Containers extension
+- GitHub Codespaces
+- Any tool that supports the Dev Container specification
+
+## Features
+
+- **Python 3.12**: Latest stable Python version
+- **Development Tools**: Pre-configured with pytest, black, mypy, ruff, and isort
+- **VS Code Extensions**:
+  - Python language support (Pylance)
+  - Black formatter
+  - Ruff linter
+  - mypy type checker
+- **Auto-formatting**: Format on save enabled
+- **Import organization**: Automatic import sorting on save
+- **Testing**: pytest configured and ready to use
+
+## Usage
+
+### VS Code
+
+1. Install the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
+2. Open this repository in VS Code
+3. When prompted, click "Reopen in Container" or use the command palette: `Dev Containers: Reopen in Container`
+4. The container will build and install all dependencies automatically
+
+### GitHub Codespaces
+
+1. Create a new Codespace from this repository
+2. The development environment will be set up automatically
+
+## Post-Create Setup
+
+After the container is created, the following command runs automatically:
+
+```bash
+pip install -e '.[dev]'
+```
+
+This installs the `agentic-devtools` package in editable mode with all development dependencies.
+
+## Customization
+
+To customize the development environment, edit the `devcontainer.json` file:
+
+- Add more VS Code extensions to the `extensions` array
+- Modify VS Code settings in the `settings` object
+- Change the Python version by updating the `image` property
+- Add additional features from the [devcontainer features catalog](https://containers.dev/features)

agentic_devtools-0.0.10/.devcontainer/devcontainer.json

@@ -0,0 +1,48 @@
+{
+	"name": "Python 3 Agentic DevTools",
+	"image": "mcr.microsoft.com/devcontainers/python:3.12",
+	
+	// Configure tool-specific properties.
+	"customizations": {
+		"vscode": {
+			"settings": {
+				"python.defaultInterpreterPath": "/usr/local/bin/python",
+				"python.linting.enabled": true,
+				"python.linting.pylintEnabled": false,
+				"python.linting.flake8Enabled": false,
+				"python.formatting.provider": "black",
+				"python.testing.pytestEnabled": true,
+				"python.testing.unittestEnabled": false,
+				"editor.formatOnSave": true,
+				"editor.codeActionsOnSave": {
+					"source.organizeImports": "explicit"
+				},
+				"[python]": {
+					"editor.defaultFormatter": "ms-python.black-formatter",
+					"editor.formatOnSave": true
+				}
+			},
+			"extensions": [
+				"ms-python.python",
+				"ms-python.vscode-pylance",
+				"ms-python.black-formatter",
+				"charliermarsh.ruff",
+				"ms-python.mypy-type-checker"
+			]
+		}
+	},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	"postCreateCommand": "pip install -e '.[dev]'",
+
+	// Configure tool-specific properties.
+	"features": {
+		"ghcr.io/devcontainers/features/git:1": {}
+	}
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

agentic_devtools-0.0.10/.dfly-temp/background-tasks/all-background-tasks.json

@@ -0,0 +1,13 @@
+[
+  {
+    "id": "21c14f00-df25-41e7-a2e0-0ee1466b50c3",
+    "command": "dfly-test",
+    "status": "failed",
+    "startTime": "2026-01-27T11:34:40.399626+00:00",
+    "endTime": "2026-01-27T11:34:40.736510+00:00",
+    "logFile": "/workspaces/agentic-devtools/.dfly-temp/background-tasks/logs/dfly_test_20260127_113440_387577.log",
+    "exitCode": 1,
+    "args": {},
+    "errorMessage": null
+  }
+]

agentic_devtools-0.0.10/.dfly-temp/dfly-state.json

@@ -0,0 +1,18 @@
+{
+  "background": {
+    "recentTasks": [
+      {
+        "id": "21c14f00-df25-41e7-a2e0-0ee1466b50c3",
+        "command": "dfly-test",
+        "status": "failed",
+        "startTime": "2026-01-27T11:34:40.399626+00:00",
+        "endTime": "2026-01-27T11:34:40.736510+00:00",
+        "logFile": "/workspaces/agentic-devtools/.dfly-temp/background-tasks/logs/dfly_test_20260127_113440_387577.log",
+        "exitCode": 1,
+        "args": {},
+        "errorMessage": null
+      }
+    ],
+    "task_id": "21c14f00-df25-41e7-a2e0-0ee1466b50c3"
+  }
+}

agentic_devtools-0.0.10/.github/MARKDOWN_LINTING.md

@@ -0,0 +1,149 @@
+# Markdown Linting Configuration Guide
+
+This document explains the markdown linting setup for the agentic-devtools repository.
+
+## Overview
+
+We use `markdownlint-cli2` to ensure consistent markdown formatting across all documentation files.
+The configuration resolves all 887 initial linting errors through a combination of:
+
+- Adjusted rule defaults
+- Directory-specific overrides
+- Strategic rule disabling for special file types
+
+## Configuration Files
+
+### Root Configuration (`.markdownlint.json`)
+
+Base rules applied to all markdown files:
+
+```json
+{
+  "MD013": { "line_length": 200 },  // Reasonable limit for documentation
+  "MD060": false,                     // Table formatting is auto-generated
+  "MD036": false,                     // Emphasis-as-heading is acceptable
+  "MD033": { "allowed_elements": [...] }  // Allow common HTML elements
+}
+```
+
+### Agent Directories (`.github/agents/`, `.github/prompts/`)
+
+AI agent files have special needs:
+
+- Contain YAML front matter → disable MD041 (first-line-heading)
+- Contain long instructional prompts → disable MD013 (line-length)
+
+### Template Directories (`.specify/templates/commands/`, `.github/scripts/speckit-trigger/templates/`)
+
+Template files also have special requirements:
+
+- Contain YAML front matter → disable MD041
+- Contain long template instructions → disable MD013
+
+## Adding New Files
+
+### Agent Files (`.agent.md`)
+
+No special action needed - the `.github/agents/.markdownlint.json` config will apply automatically.
+
+### Prompt Files (`.prompt.md`)
+
+No special action needed - the `.github/prompts/.markdownlint.json` config will apply automatically.
+
+### Template Files
+
+Place in appropriate template directory where MD041 and MD013 are disabled.
+
+### Regular Documentation
+
+Follow these guidelines:
+
+- Keep lines under 200 characters
+- Add blank lines around lists, headings, and code blocks
+- Specify language for code blocks (use `text` for plain text)
+- Wrap bare URLs in backticks or use markdown links
+
+## Running the Linter
+
+### Locally
+
+```bash
+npx markdownlint-cli2 "**/*.md"
+```
+
+### Auto-fix
+
+Many issues can be auto-fixed:
+
+```bash
+npx markdownlint-cli2 --fix "**/*.md"
+```
+
+### CI/CD
+
+The linter runs automatically on all PRs via `.github/workflows/lint.yml`.
+
+## Common Issues and Solutions
+
+### MD041: First line should be H1
+
+**Problem**: File starts with YAML front matter or H2
+**Solution**: Add `.markdownlint.json` to the directory with `"MD041": false`
+
+### MD013: Line too long
+
+**Problem**: Line exceeds 200 characters
+**Solutions**:
+
+1. Break the line naturally at a clause or phrase boundary
+2. If in a template/agent file, ensure MD013 is disabled for that directory
+
+### MD040: Code block needs language
+
+**Problem**: Code block has ` ``` ` without language specifier
+**Solution**: Add appropriate language:
+
+- ` ```bash ` for shell commands
+- ` ```python ` for Python code
+- ` ```text ` for plain text or examples
+- ` ```json ` for JSON data
+
+### MD031/MD032: Missing blank lines
+
+**Problem**: Lists or code blocks not surrounded by blank lines
+**Solution**: Run `npx markdownlint-cli2 --fix "**/*.md"` - this is auto-fixable
+
+## Configuration Rationale
+
+### Why 200 character line limit?
+
+- 120 was too restrictive for documentation
+- 200 allows natural sentence flow while preventing excessive line length
+- Code blocks and tables are excluded from the limit
+
+### Why disable MD013 for agents/templates?
+
+These files contain AI prompts and instructions that:
+
+- Often need to be continuous for clarity
+- Are optimized for AI readability, not human line-length preferences
+- Would be awkward if artificially broken
+
+### Why disable MD041 for files with YAML front matter?
+
+YAML front matter is a standard pattern for:
+
+- GitHub Copilot agent definitions
+- Jekyll/Hugo/static site generators
+- Metadata in markdown files
+
+The first "content" line after front matter may legitimately be H2 or other elements.
+
+## Future Maintenance
+
+When adding new markdown files:
+
+1. Run the linter: `npx markdownlint-cli2 "path/to/new/file.md"`
+2. For one-off exceptions, add an HTML comment: `<!-- markdownlint-disable MD### -->`
+3. For directory patterns, create a `.markdownlint.json` in that directory
+4. Document the reason for any exceptions in this file

agentic_devtools-0.0.10/.github/agents/.markdownlint.json

@@ -0,0 +1,6 @@
+{
+  "$schema": "https://raw.githubusercontent.com/DavidAnson/markdownlint/main/schema/markdownlint-config-schema.json",
+  "extends": "../../.markdownlint.json",
+  "MD041": false,
+  "MD013": false
+}

agentic_devtools-0.0.10/.github/agents/agdt.apply-pr-suggestions.initiate.agent.md

@@ -0,0 +1,40 @@
+---
+description: "Apply PR Suggestions - Initiate: Apply PR review suggestions"
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Start the apply PR suggestions workflow.
+
+## Prerequisites
+
+- **Required state**: `pull_request_id`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set pull_request_id <value>
+  ```
+
+## Actions
+
+1. Initiate apply PR suggestions:
+
+   ```bash
+   agdt-initiate-apply-pr-suggestions-workflow
+   ```
+
+## Expected Outcome
+
+The workflow starts and is ready to apply suggestions.
+
+## Next Step
+
+Workflow is complete.

agentic_devtools-0.0.10/.github/agents/agdt.create-jira-epic.initiate.agent.md

@@ -0,0 +1,42 @@
+---
+description: "Create Jira Epic - Initiate: Create a new Jira epic"
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Start the create-jira-epic workflow and capture epic details.
+
+## Prerequisites
+
+- **Required state**: `jira.project_key`, `jira.summary`, `jira.epic_name`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set jira.project_key <value>
+  agdt-set jira.summary <value>
+  agdt-set jira.epic_name <value>
+  ```
+
+## Actions
+
+1. Initiate epic creation:
+
+   ```bash
+   agdt-initiate-create-jira-epic-workflow
+   ```
+
+## Expected Outcome
+
+A Jira epic is created or the workflow is ready for inputs.
+
+## Next Step
+
+Workflow is complete.

agentic_devtools-0.0.10/.github/agents/agdt.create-jira-issue.initiate.agent.md

@@ -0,0 +1,42 @@
+---
+description: "Create Jira Issue - Initiate: Create a new Jira issue"
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Start the create-jira-issue workflow and capture issue details.
+
+## Prerequisites
+
+- **Required state**: `jira.project_key`, `jira.summary`, `jira.description`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set jira.project_key <value>
+  agdt-set jira.summary <value>
+  agdt-set jira.description <value>
+  ```
+
+## Actions
+
+1. Initiate issue creation:
+
+   ```bash
+   agdt-initiate-create-jira-issue-workflow
+   ```
+
+## Expected Outcome
+
+A Jira issue is created or the workflow is ready for inputs.
+
+## Next Step
+
+Workflow is complete.

agentic_devtools-0.0.10/.github/agents/agdt.create-jira-subtask.initiate.agent.md

@@ -0,0 +1,42 @@
+---
+description: "Create Jira Subtask - Initiate: Create a Jira subtask"
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Start the create-jira-subtask workflow and capture subtask details.
+
+## Prerequisites
+
+- **Required state**: `jira.parent_key`, `jira.summary`, `jira.description`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set jira.parent_key <value>
+  agdt-set jira.summary <value>
+  agdt-set jira.description <value>
+  ```
+
+## Actions
+
+1. Initiate subtask creation:
+
+   ```bash
+   agdt-initiate-create-jira-subtask-workflow
+   ```
+
+## Expected Outcome
+
+A Jira subtask is created or the workflow is ready for inputs.
+
+## Next Step
+
+Workflow is complete.

agentic_devtools-0.0.10/.github/agents/agdt.pull-request-review.completion.agent.md

@@ -0,0 +1,40 @@
+---
+description: "PR Review - Completion: Finalize review (step 5 of 5)"
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Finalize the review and add any Jira follow-up comment.
+
+## Prerequisites
+
+- **Required state**: `pull_request_id`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set pull_request_id <value>
+  ```
+
+## Actions
+
+1. Post a Jira follow-up comment:
+
+   ```bash
+   agdt-add-jira-comment
+   ```
+
+## Expected Outcome
+
+The PR review workflow is completed.
+
+## Next Step
+
+Workflow is complete.

agentic_devtools-0.0.10/.github/agents/agdt.pull-request-review.decision.agent.md

@@ -0,0 +1,51 @@
+---
+description: "PR Review - Decision: Approve or request changes (step 4 of 5)"
+handoffs:
+  - label: "Continue to Completion"
+    agent: "agdt.pull-request-review.completion"
+    prompt: "Finalize the review."
+
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Decide whether to approve or request changes for the pull request.
+
+## Prerequisites
+
+- **Required state**: `pull_request_id`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set pull_request_id <value>
+  ```
+
+## Actions
+
+1. Approve the pull request:
+
+   ```bash
+   agdt-approve-pull-request
+   ```
+
+2. Request changes with a comment:
+
+   ```bash
+   agdt-add-pull-request-comment
+   ```
+
+## Expected Outcome
+
+The review decision is recorded and the workflow moves to completion.
+
+## Next Step
+
+Continue to completion.

agentic_devtools-0.0.10/.github/agents/agdt.pull-request-review.file-review.agent.md

@@ -0,0 +1,55 @@
+---
+description: "PR Review - File Review: Review individual files (step 2 of 5)"
+handoffs:
+  - label: "Continue File Review"
+    agent: "agdt.pull-request-review.file-review"
+    prompt: "Review the next file."
+  - label: "Continue to Summary"
+    agent: "agdt.pull-request-review.summary"
+    prompt: "Generate the review summary."
+
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Review files and record approvals or requested changes.
+
+## Prerequisites
+
+- **Required state**: `pull_request_id`, `file_review.file_path`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set pull_request_id <value>
+  agdt-set file_review.file_path <value>
+  ```
+
+## Actions
+
+1. Approve the file:
+
+   ```bash
+   agdt-approve-file
+   ```
+
+2. Request changes:
+
+   ```bash
+   agdt-request-changes
+   ```
+
+## Expected Outcome
+
+File review feedback is recorded and the queue advances.
+
+## Next Step
+
+Continue file review or move to summary.

agentic_devtools-0.0.10/.github/agents/agdt.pull-request-review.initiate.agent.md

@@ -0,0 +1,46 @@
+---
+description: "PR Review - Initiate: Start a pull request review (step 1 of 5)"
+handoffs:
+  - label: "Continue to File Review"
+    agent: "agdt.pull-request-review.file-review"
+    prompt: "Review individual files."
+
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Start the pull-request-review workflow and load PR context.
+
+## Prerequisites
+
+- **Required state**: `pull_request_id`, `jira.issue_key`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set pull_request_id <value>
+  agdt-set jira.issue_key <value>
+  ```
+
+## Actions
+
+1. Start the PR review:
+
+   ```bash
+   agdt-review-pull-request
+   ```
+
+## Expected Outcome
+
+The review workflow starts and prepares the file review queue.
+
+## Next Step
+
+Continue to file review.

agentic_devtools-0.0.10/.github/agents/agdt.pull-request-review.summary.agent.md

@@ -0,0 +1,45 @@
+---
+description: "PR Review - Summary: Generate review summary (step 3 of 5)"
+handoffs:
+  - label: "Continue to Decision"
+    agent: "agdt.pull-request-review.decision"
+    prompt: "Approve or request changes."
+
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Generate the pull request review summary.
+
+## Prerequisites
+
+- **Required state**: `pull_request_id`
+- **Set state** (if not already set):
+
+  ```bash
+  agdt-set pull_request_id <value>
+  ```
+
+## Actions
+
+1. Generate the summary:
+
+   ```bash
+   agdt-generate-pr-summary
+   ```
+
+## Expected Outcome
+
+A review summary is generated and ready for a decision.
+
+## Next Step
+
+Continue to decision.