github.com/jocmp/capyreader (link)

commit signals (0)

none

source signals (10)

• File: .claude/skills/profile-select/SKILL.mdTool: unspecified

  Run the bench select-profile command and format the output as a table.
  
  1. Ensure bench data exists (if not, run `make bench-reset` then `./gradlew :bench:run --args="refresh"`)
  2. Run `./gradlew :bench:run --args="select-profile"`
  3. Parse the output and present the timing results in a markdown table
  

• File: .claude/skills/gh-issue/SKILL.mdTool: unspecified

  Please analyze and address the GitHub issue: $ARGUMENTS.
  
  Follow these steps:
  
  1. Use `gh issue view` to get the issue details
  2. Understand the problem described in the issue
  3. **Planning (optional for trivial tasks)**: If the task involves multiple files, architectural decisions, or unclear requirements, enter planning mode to explore the codebase and design an approach before implementing. Skip this step for simple fixes like typos, single-line changes, or obvious bugs.
  4. Search the codebase for releva

• File: .claude/skills/fix-weblate/SKILL.mdTool: unspecified

  1. Open an existing checkout of the upstream repository or perform a fresh one.
  2. Commit all pending changes in Weblate and lock the translation component.
      ```
      wlc commit capy-reader/strings; wlc lock capy-reader/strings
      ```
  3. Add Weblate exported repository as a remote.
      ```
      git remote add weblate https://hosted.weblate.org/git/capy-reader/strings/ ; git remote update weblate
      ```
  4. Merge Weblate changes and resolve any conflicts.
      ```
      git merge weblate/main
      ```
  5. Push 

• File: .claude/skills/profile-refresh/SKILL.mdTool: unspecified

  Run the bench refresh-profile command and format the output as a table.
  
  1. Run `make bench-reset`
  2. Run `make bench-profile`
  3. Parse the output and present the timing results in a markdown table
  

• File: AGENTS.mdTool: agents-md

  # AGENTS.md
  
  **Stop. Read the [README.md](./README.md) before doing anything.**
  
  If you are an AI agent or a contributor using AI-assisted tooling, you must read and follow the contributing guidelines in the README before opening a pull request.
  
  Key points:
  
  - **Ask before submitting a PR.** Do not open unsolicited pull requests. See the [Pull Requests](./README.md#pull-requests) section.
  - **Search existing discussions and issues first.** Do not create duplicate reports or requests.
  - **Follow the project

• File: CLAUDE.mdTool: claude-code

  # CLAUDE.md
  
  ## Build and Development
  
  - `./gradlew assembleFreeDebug` will compile the debug version of the app
  - For fast feedback, run single tests i.e. `./gradlew :capy:test --tests com.jocmp.capy.persistence.ArticleRecordsTest` replacing the module - `:capy` - and Java package accordingly. Note `:capy` is a JVM module (use `:capy:test`); Android modules like `:app` use the variant task `testFreeDebugUnitTest`
  - `make test` will run all tests via Fastlane.
  - When modifying the `.js` and `.liquid` files,

• Dir: .claudeTool: claude-code
• Dir: .claudeTool: claude-code
• Dir: .claudeTool: claude-code
• Dir: .claudeTool: claude-code

ignorefile signals (0)

none