agentleFS
Sign inStart free
xsovad06xsovad06/sova/.agents/skills/sova-issue/SKILL.md

sova-issue

Skill3 starsChanged 5 days agoApache-2.0View on GitHub

Fetch and analyze a task from the project tracker.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ready to implement?: Run the sova-develop-full skill <ISSUE_NUMBER>

    line 37
  2. Very specific:

    Want a spec first?: Run the sova-spec skill <ISSUE_NUMBER>

    line 38
  3. Very specific:

    Planning your sprint?: Run the sova-find-task skill

    line 39
  4. Distinctive:

    NEVER use emojis in any output

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Issue

Fetch and analyze a task from the project tracker.

Instructions

  1. Get the issue number or ticket key from the arguments provided when this skill is invoked. If empty, ask the user.
  2. Determine the task source by running sova config and reading the task_source row (configuration lives in .claude/sova.db, not in a file).

  3. Fetch the task:

    GitHub (the default):

    gh issue view <arguments> --json number,title,state,assignees,labels,milestone,body,comments

    JIRA (task_source.type = "jira"):

    jira issue view <arguments> --plain
  4. Present:
    • Title, status, assignees, labels/components, milestone/sprint
    • Description (summarized if long)
    • Comments or activity (key discussion points)
    • Related/linked issues (mentioned in body, comments, or JIRA links)
    • Suggested approach for implementation

Cross-References

  • Ready to implement? Run the sova-develop-full skill <ISSUE_NUMBER>
  • Want a spec first? Run the sova-spec skill <ISSUE_NUMBER>
  • Planning your sprint? Run the sova-find-task skill

Rules

  • NEVER use emojis in any output

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free