@datatamer.ai/agentdev 1.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json ADDED
@@ -0,0 +1,51 @@
1
+ {
2
+ "name": "@datatamer.ai/agentdev",
3
+ "version": "1.0.1",
4
+ "description": "AgentDev distributed agent client for processing GitHub tickets",
5
+ "type": "module",
6
+ "main": "src/index.js",
7
+ "bin": {
8
+ "agentdev": "./dist/agentdev.js"
9
+ },
10
+ "files": [
11
+ "dist/agentdev.js",
12
+ "skills/"
13
+ ],
14
+ "engines": {
15
+ "node": ">=18.0.0"
16
+ },
17
+ "scripts": {
18
+ "build": "node scripts/build.js",
19
+ "deploy": "bash scripts/deploy.sh",
20
+ "prepublishOnly": "npm run build",
21
+ "test": "echo \"No tests yet\" && exit 0"
22
+ },
23
+ "keywords": [
24
+ "agent",
25
+ "distributed",
26
+ "github",
27
+ "automation",
28
+ "workflow"
29
+ ],
30
+ "author": "DataTamer",
31
+ "license": "MIT",
32
+ "dependencies": {
33
+ "@fission-ai/openspec": "latest",
34
+ "commander": "^12.0.0",
35
+ "axios": "^1.6.0",
36
+ "chalk": "^5.3.0",
37
+ "ora": "^8.0.0",
38
+ "conf": "^12.0.0",
39
+ "remotion": "^4.0.419",
40
+ "@remotion/cli": "^4.0.419",
41
+ "@remotion/renderer": "^4.0.419"
42
+ },
43
+ "devDependencies": {
44
+ "esbuild": "^0.24.0",
45
+ "javascript-obfuscator": "^4.1.0"
46
+ },
47
+ "repository": {
48
+ "type": "git",
49
+ "url": "https://github.com/data-tamer/agentdev"
50
+ }
51
+ }
@@ -0,0 +1,62 @@
1
+ # agentdev gh — GitHub CLI
2
+
3
+ Use `agentdev gh` for ALL GitHub operations. Do NOT use `gh` directly.
4
+ GH_TOKEN is pre-configured in your environment.
5
+
6
+ ## Issue Commands
7
+
8
+ ```bash
9
+ # View an issue (JSON output)
10
+ agentdev gh issue view <number> -R <owner/repo> --json title,body,state,labels,author
11
+
12
+ # Create an issue
13
+ agentdev gh issue create -R <owner/repo> --title "Title" --body "Body text"
14
+ agentdev gh issue create -R <owner/repo> --title "Title" --body-file /path/to/body.md
15
+
16
+ # Comment on an issue
17
+ agentdev gh issue comment <number> -R <owner/repo> --body "Comment text"
18
+ agentdev gh issue comment <number> -R <owner/repo> --body-file /path/to/comment.md
19
+
20
+ # Reopen a closed issue
21
+ agentdev gh issue reopen <number> -R <owner/repo>
22
+ ```
23
+
24
+ ## Pull Request Commands
25
+
26
+ ```bash
27
+ # Create a PR
28
+ agentdev gh pr create -R <owner/repo> --title "PR title" --body "Description" --head feature-branch --base master
29
+
30
+ # View a PR (JSON output)
31
+ agentdev gh pr view <number> -R <owner/repo> --json title,body,state,head,base,mergeable
32
+
33
+ # Merge a PR
34
+ agentdev gh pr merge <number> -R <owner/repo> --squash
35
+ agentdev gh pr merge <number> -R <owner/repo> --rebase
36
+ agentdev gh pr merge <number> -R <owner/repo> --merge
37
+ ```
38
+
39
+ ## Project Board Commands
40
+
41
+ ```bash
42
+ # Update a project item field (e.g., change status)
43
+ agentdev gh project item-edit --id <item-id> --project-id <project-id> --field-id <field-id> --single-select-option-id <option-id>
44
+ ```
45
+
46
+ ## Raw API Commands
47
+
48
+ ```bash
49
+ # GraphQL query
50
+ agentdev gh api graphql -f query='{ viewer { login } }'
51
+
52
+ # REST API call
53
+ agentdev gh api rest /repos/owner/repo/issues -X GET
54
+ agentdev gh api rest /repos/owner/repo/issues -X POST --input body.json
55
+ ```
56
+
57
+ ## Notes
58
+
59
+ - All repos are under the `data-tamer` organization
60
+ - Always use `-R data-tamer/<repo>` format
61
+ - Use `--json` flag for machine-readable output when parsing results
62
+ - Use `--body-file` for long content to avoid shell escaping issues
@@ -0,0 +1,72 @@
1
+ # agentdev openspec — Spec-Driven Development
2
+
3
+ Use `agentdev openspec` for ALL OpenSpec operations. Do NOT use `openspec` directly.
4
+ OpenSpec is bundled with agentdev — no separate install needed.
5
+
6
+ ## Setup
7
+
8
+ ```bash
9
+ # Initialize OpenSpec in the current project
10
+ agentdev openspec init --tools claude-code
11
+
12
+ # Update instruction files after CLI upgrades
13
+ agentdev openspec run update --force
14
+ ```
15
+
16
+ ## Workflow
17
+
18
+ When processing a ticket, follow this spec-driven workflow:
19
+
20
+ 1. **Check status** — see what artifacts exist
21
+ 2. **Get instructions** — get guidance for the next artifact to create
22
+ 3. **Create artifacts** — proposal → specs → design → tasks → apply
23
+ 4. **Validate** — check structural integrity
24
+ 5. **Archive** — merge deltas into specs when done
25
+
26
+ ## Commands
27
+
28
+ ```bash
29
+ # Check artifact completion status
30
+ agentdev openspec status --json
31
+ agentdev openspec status --change my-change --json
32
+
33
+ # List all changes or specs
34
+ agentdev openspec list --json
35
+ agentdev openspec list --specs --json
36
+
37
+ # Show details of a specific change or spec
38
+ agentdev openspec show my-change --json
39
+ agentdev openspec show my-change --deltas-only
40
+ agentdev openspec show my-spec --type spec --requirements
41
+
42
+ # Get creation instructions for next artifact
43
+ agentdev openspec instructions proposal --change my-change --json
44
+ agentdev openspec instructions design --change my-change --json
45
+ agentdev openspec instructions tasks --change my-change --json
46
+ agentdev openspec instructions apply --change my-change --json
47
+
48
+ # Validate changes and specs
49
+ agentdev openspec validate --all --json
50
+ agentdev openspec validate my-change --strict --json
51
+
52
+ # Archive a completed change (merges deltas into specs)
53
+ agentdev openspec archive my-change --yes
54
+
55
+ # View available workflow schemas
56
+ agentdev openspec run schemas
57
+ ```
58
+
59
+ ## Artifact Flow
60
+
61
+ ```
62
+ proposal.md → specs (deltas) → design.md → tasks.md → apply (implement)
63
+ ```
64
+
65
+ Each artifact builds on the previous one. Use `--json` output to parse status programmatically and determine the next step.
66
+
67
+ ## Notes
68
+
69
+ - Always use `--json` flag when parsing output programmatically
70
+ - Use `agentdev openspec status --json` to determine workflow progress
71
+ - The `instructions` command provides templates and context for creating each artifact
72
+ - Archive changes after implementation to keep specs up to date