Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .kiro/specs/kiroween-submission/design.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ Rejected: moving the server into the Power and resolving packages from the paren
"name": "gitgotchi",
"version": "1.0.0",
"description": "Diagnose and heal a GitGotchi repo pet from Kiro: pet status, findings, feed, clean and the summon-healer skill.",
"author": { "name": "Rizick", "url": "https://github.com/Zee7X" },
"author": { "name": "Zee7X", "url": "https://github.com/Zee7X" },
"keywords": ["gitgotchi", "repo pet", "repo health", "summon healer", "code smell", "failing ci"],
"repository": "https://github.com/Zee7X/gitgochi",
"license": "MIT"
Expand Down
2 changes: 1 addition & 1 deletion .kiro/specs/kiroween-submission/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Out of scope: a GitHub Actions workflow for this repository, accounts or OAuth,
1. THE Agent SHALL add the remote `origin` with URL `https://github.com/Zee7X/gitgochi.git` to the Repository.
2. WHEN `origin/main` has been fetched, THE Agent SHALL merge `origin/main` into local `main` with `--allow-unrelated-histories`.
3. WHEN the merge conflicts on `README.md`, THE Agent SHALL keep the local version of `README.md`.
4. WHEN the merge conflicts on `LICENSE`, THE Agent SHALL keep the remote version of `LICENSE` (MIT License, "Copyright (c) 2026 Rizick").
4. WHEN the merge conflicts on `LICENSE`, THE Agent SHALL keep the remote version of `LICENSE` (MIT License, "Copyright (c) 2026 Zee7X").
5. WHEN the Agent prepares a push, THE Agent SHALL confirm that `git ls-files .kiro` lists the Feature_Specs, the steering files, the hook files and `.kiro/settings/mcp.json`, and that `.env.example` is the only tracked file whose name starts with `.env`.
6. WHEN the merge commit exists, THE Agent SHALL push `main` to Origin with `git push origin main` and no force option.
7. IF Origin rejects a push, THEN THE Agent SHALL stop pushing and report the rejection message to the User.
Expand Down
2 changes: 1 addition & 1 deletion LICENSE
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2026 Rizick
Copyright (c) 2026 Zee7X

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ The `.kiro/` folder is at the repository root and is committed. The full write-u
| MCP server | `mcp-server/index.mjs`, `.kiro/settings/mcp.json` | stdio server `gitgotchi` with `get_pet_status`, `diagnose_pet`, `feed_pet`, `clean_pet`, `simulate_event` (demo repos only), `adopt_pet` and `add_badge` (writes the badge into the workspace README; you commit). The other tools call the running app over HTTP. Only the two read-only tools are auto-approved |
| Property-based tests | `src/lib/__tests__/state-machine.test.ts` | `fast-check` properties P1 to P6 run the engine over random event sequences and time gaps. The pet-engine requirements name the property that checks each rule |
| Kiro Power | `power-gitgotchi/` | The MCP server bundled as one file plus the `summon-healer` skill, so another workspace can add GitGotchi as a Power. `power.test.ts` checks the bundle lists the same tools as the source |
| Kiro IDE, then Kiro Web | git history: `Rizick` / `Zee7X` commits (IDE), `Kiro Agent` commits and PRs #1 to #24 (Web) | In the Kiro IDE I wrote the PRD and BRD and Kiro ran the spec tasks that built the engine, handheld UI, hooks and MCP server. I moved to Kiro Web to work directly with GitHub and Vercel, with far fewer approvals. Deployment, the GitHub App, accounts and privacy, the NECROMANCER stage and the CI workflow were built in Kiro Web agent sessions: spec first, then code and tests, each change through a pull request with CI and a production check. Details in [docs/KIRO_USAGE.md](docs/KIRO_USAGE.md) |
| Kiro IDE, then Kiro Web | git history: `Zee7X` commits (IDE), `Kiro Agent` commits and PRs #1 to #24 (Web) | In the Kiro IDE I wrote the PRD and BRD and Kiro ran the spec tasks that built the engine, handheld UI, hooks and MCP server. I moved to Kiro Web to work directly with GitHub and Vercel, with far fewer approvals. Deployment, the GitHub App, accounts and privacy, the NECROMANCER stage and the CI workflow were built in Kiro Web agent sessions: spec first, then code and tests, each change through a pull request with CI and a production check. Details in [docs/KIRO_USAGE.md](docs/KIRO_USAGE.md) |

**Summon Kiro** runs from HEAL on the handheld, from `diagnose_pet` over MCP, or from `/summon-healer` in Kiro chat. It reports the latest completed CI run if that run failed (with its link, the failed jobs and steps, and an excerpt of the failing log), up to 3 stale issues, up to 5 code smells reported by the hook, and the days since the last push when there has been no push for 2 days or more. It returns those findings and a prompt. The prompt marks log lines, issue titles and file names as untrusted repository data, so text planted in a CI log cannot steer Kiro. Kiro then fixes the code in your workspace and runs `npm test`. GitGotchi does not open pull requests and does not edit files.

Expand Down Expand Up @@ -298,4 +298,4 @@ GitHub Actions (`.github/workflows/ci.yml`) runs lint, the type check and the un

## License

MIT License, Copyright (c) 2026 Rizick. See [LICENSE](LICENSE).
MIT License, Copyright (c) 2026 Zee7X. See [LICENSE](LICENSE).
2 changes: 1 addition & 1 deletion docs/KIRO_USAGE.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The Devpost "How did you use Kiro?" write-up. Each answer points at files in thi

## Kiro Web: the second half of the build

The first half (engine, UI, hooks, MCP server) was built in the **Kiro IDE**: I wrote the PRD and BRD and Kiro ran the spec tasks (commits by `Rizick` and `Zee7X`). Everything after it was built in **Kiro Web** agent sessions: the commits authored by `Kiro Agent` and pull requests #1 to #23. This section was written from that session's own record and every claim points at a PR, a spec line or a test.
The first half (engine, UI, hooks, MCP server) was built in the **Kiro IDE**: I wrote the PRD and BRD and Kiro ran the spec tasks (commits by `Zee7X`). Everything after it was built in **Kiro Web** agent sessions: the commits authored by `Kiro Agent` and pull requests #1 to #23. This section was written from that session's own record and every claim points at a PR, a spec line or a test.

**How a change was made.** The same loop for every feature: write or change the spec (EARS requirement plus a task), then the code, then a test that fails without the change, then a pull request that only merges when GitHub Actions and the Vercel preview are green, then a check against the production site. Examples:

Expand Down
2 changes: 1 addition & 1 deletion power-gitgotchi/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"name": "gitgotchi",
"version": "1.0.0",
"description": "Diagnose and heal a GitGotchi repo pet from Kiro: pet status, findings, feed, clean and the summon-healer skill.",
"author": { "name": "Rizick", "url": "https://github.com/Zee7X" },
"author": { "name": "Zee7X", "url": "https://github.com/Zee7X" },
"keywords": ["gitgotchi", "repo pet", "repo health", "summon healer", "code smell", "failing ci"],
"repository": "https://github.com/Zee7X/gitgochi",
"license": "MIT"
Expand Down
Loading