chore: release v0.2.7

[devin-ai-integration]

Summary

Bump version 0.2.6 → 0.2.7 for release. Only changes Cargo.toml version field and Cargo.lock.

Link to Devin session: https://app.devin.ai/sessions/9c05871e14e84779b12a3b96a7669c01
Requested by: @sachiniyer

---

Summary by cubic

Prepare v0.2.7 release for detail-cli by bumping the version from 0.2.6 to 0.2.7. Only updates Cargo.toml and Cargo.lock; no functional changes.

^{Written for commit 627de3a. Summary will update on new commits.}

[devin-ai-integration]

Original prompt from Sachin

Siddhartha Mishra [4:06 PM]
the cli only installs skills inside a repo? ideally I would move them to my user level skills so I can use them everywhere. is that a conscious choice?
Dan Robinson [4:07 PM]
Nah just an oversight on our part. We keep our skills inside our monorepo.
Dan Robinson [4:07 PM]
It's just a markdown so worst case you can take it with you / move it wherever.
Siddhartha Mishra [4:07 PM]
yeah will do
Dan Robinson [4:08 PM]
Is there a standard location for these skills to go?
Dan Robinson [4:08 PM]
also just saw a bunch of the bugs detail had flagged in that repo, had never logged into the detail dashboard before lol so will work through some of those as wellOk there is definitely something to be learned here. For future ref, if you go in to Settings > Repositories > repo you should be able to set it up to automatically send future bugs on that repo to Linear or Slack or github or ...

Let us know what you notice! (Any of them any good? Noisy? Other takes?)
Siddhartha Mishra [4:09 PM]
i just want the skills to go in my ~/.claude/skills so I can access them anywhere
Dan Robinson [4:09 PM]
cc @Sachin Iyer ^
Sachin Iyer [4:11 PM]
i just want the skills to go in my ~/.claude/skills so I can access them anywhere

will fix!

Can you add a flag to allow installing skills in the user level configuration instead

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.